http://bugs.codeweavers.com/show_bug.cgi?id=622
*** shadow/622 Thu Apr 25 19:59:02 2002 --- shadow/622.tmp.27996 Thu Apr 25 19:59:02 2002 *************** *** 0 **** --- 1,42 ---- + +============================================================================+ + | aol7 cannot communicate with the aol proxy server | + +----------------------------------------------------------------------------+ + | Bug #: 622 Product: Wine | + | Status: UNCONFIRMED Version: 20020411 | + | Resolution: Platform: | + | Severity: normal OS/Version: All | + | Priority: P1 Component: wine-net | + +----------------------------------------------------------------------------+ + | Assigned To: wine-bugs@winehq.com | + | Reported By: michaelc@lindows.com | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | Milestone: TargetMilestone: --- | + | URL: | + +============================================================================+ + | DESCRIPTION | + I've been working on trying to figure out why aol7 doesn't work under wine + for a few weeks, but I was using the old code up until now. Actually, with + the current wine tree, you can launch aol and login, but you can't get any + web content or your buddy list. I think that both of these operations go + through aol's web proxies and require a successful handshake with the proxy + to succeed. + + Basically, what I know is that aol7 uses asynchronous sockets, but doesn't + seem to use overlapped io, unless you're on a modem. When aol is trying to + connect to it's web proxy it only sends one packet out when running under + wine, and then after a while gets an ACK packet in response from the proxy. + The one packet that gets sent is completely identical to the one sent under + windows. Under windows, it actually sends out three packets in rapid + succession, and then gets a response from the proxy. The packets sent are + using the AIM protocol and can be examined using ethereal under windows and + under linux. The handshake between the aol client and the proxy is as follows: + + client -> AIM packet, family: 0x5472 + client -> AIM packet, family: 0x5472 + client -> AIM packet, family: 0x7963 + proxy -> AIM packet, family: 0x7963 + + I looked at the return code from ws2_32.send and it claims that the requested + number of bytes were sent successfully. Also, there are no obvious errors + around the time that the handshake packets are sent. \ No newline at end of file