On Tue, 15 Jan 2013, Daniel Stenberg wrote:
I'm on the 1059 issue now.
I run this and compare the traces and that tells Curl_proxyCONNECT() seems to
not be working entirely correct for you, although I haven't been able to
pinpoint why/how.
Your trace says after the CONNECT response:
18:39:38.693556 <= Recv header, 19 bytes (0x13)
0000: Content-Length: 0
18:39:38.693556 <= Recv header, 2 bytes (0x2)
0000:
18:39:38.693556 == Info: 0xb5f1a0 is at send pipe head!
18:39:38.693556 == Info: STATE: CONNECT => WAITPROXYCONNECT handle 0xb82f68;
line 1029 (connection #0)
18:39:38.713556 == Info: Multi mode finished polling for response from proxy
CONNECT
18:39:38.713556 == Info: Proxy CONNECT aborted
While my log says:
23:07:24.111203 <= Recv header, 19 bytes (0x13)
0000: Content-Length: 0
23:07:24.112317 <= Recv header, 2 bytes (0x2)
0000:
23:07:24.118289 == Info: Received HTTP code 501 from proxy after CONNECT
23:07:24.129116 == Info: Closing connection 0
To me it looks as if in your case it doesn't properly detect the end of the
response (headers) so it continues to wait and then eventually the connection
gets closed and it gets upset.
Can you sprinkle some debug logs in there to see if you can figure it out?
--
/ daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
