Re: HTTP response is Connection: close
FWIW, if Polipo can detect such a situation (either because we haven't reached the Content-Length the server declared, or because there was an unterminated chunk), it will refetch the object. The responses in question are completely empty, there's not a single HTTP header and of course the nothingness isn't chunked either. Then you should get a « 502 Server dropped connection » error. If you don't, please report it as a bug. I get the impression that Polipo forwards them as empty page and puts some headers on top. This shouldn't happen -- unless Polipo's immediate upstream happens to be an HTTP/1.0 implementation. (Even if the upstream is HTTP/1.0, this should only happen if the upstream sends no Content-Length *and* the connection is broken just after the CR-LF-CR-LF that ends the headers.) Please let me state this once more. HTTP/1.0 is obsolete, it is slow, it is unreliable. I've done my best to make HTTP/1.0 reasonably reliable in Polipo, but there's really not much that one can hack around with such a deficient protocol. (Note that, since HTTP/1.1 is backwards compatible with 1.0, it is possible to send an HTTP/1.0 reply with an HTTP/1.1 header.) At least I'm currently running Privoxy-Polipo-Tor as default proxy chain Then don't do that. Privoxy is downgrading perfectly good HTTP/1.1 replies down to the old, unreliable, HTTP/1.0 kind. (Note that it does tag them with « HTTP/1.1 », which it is perfectly allowed to do.) Tested with Privoxy 3.0.6. Refreshing with CTRL+F5 usually results in the real page. Yes, there's a special hack to ensure that objects served as HTTP/1.0 are less sticky than normal. (File server.c line 2086.) Juliusz
Re: HTTP response is Connection: close
Juliusz Chroboczek [EMAIL PROTECTED] wrote: Like Andrew, I assume the real problem is a malfunctioning intercepting proxy on the exit node, so there's little you can do about it. I would rather blame it on a tor server that crashes or drops the connection. It's my impression that the OP can detect that and throws a socks error. If, however, there's a broken intercepting proxy it would explain why the OP doesn't notice. WWIW, if Polipo can detect such a situation (either because we haven't reached the Content-Length the server declared, or because there was an unterminated chunk), it will refetch the object. The responses in question are completely empty, there's not a single HTTP header and of course the nothingness isn't chunked either. I get the impression that Polipo forwards them as empty page and puts some headers on top. At least I'm currently running Privoxy-Polipo-Tor as default proxy chain and from time to time I get empty pages that pass Privoxy's trivial no-data check. Refreshing with CTRL+F5 usually results in the real page. I neither verified that it's the same problem, nor did I check how the requests look like before they reach Polipo or after they are processed by it, but the symptoms would fit. Fabian signature.asc Description: PGP signature
Re: HTTP response is Connection: close
Got Glint [EMAIL PROTECTED] wrote: Sometimes when I perform an HTTP request via Tor, the response is Connection: close rather than the expected content. This happens intermittently, and with various sites. Does anyone know what causes this problem, and whether anything can be done about it? It's been annoying me for quite a while. I've experienced the issue with at least two clients: Opera and Wget. They both interpret the response body as a 21-byte string consisting of Connection: close\r\n\r\n. Also, Wget says 200 No headers, assuming HTTP/0.9. Current software versions: Tor 0.1.2.14, Privoxy 3.0.6, Windows XP SP2. This can happen with Privoxy versions before 3.0.7 and a server or proxy before Privoxy that simply sends nothing. You should be able to reliable reproduce it by using Tor's .noconnect special host name (although it's a slightly different case). As far as Privoxy is concerned, this has been fixed in: http://ijbswa.cvs.sourceforge.net/ijbswa/current/jcc.c?r1=1.118r2=1.119 However, this of course only replaces the confusing Connection: close string with a more reasonable problem description. The real problem happens earlier in the proxy chain and you still have to retry manually. Like Andrew, I assume the real problem is a malfunctioning intercepting proxy on the exit node, so there's little you can do about it. Fabian signature.asc Description: PGP signature
Re: HTTP response is Connection: close
Like Andrew, I assume the real problem is a malfunctioning intercepting proxy on the exit node, so there's little you can do about it. I would rather blame it on a tor server that crashes or drops the connection. WWIW, if Polipo can detect such a situation (either because we haven't reached the Content-Length the server declared, or because there was an unterminated chunk), it will refetch the object. Juliusz
HTTP response is Connection: close
Sometimes when I perform an HTTP request via Tor, the response is Connection: close rather than the expected content. This happens intermittently, and with various sites. Does anyone know what causes this problem, and whether anything can be done about it? It's been annoying me for quite a while. I've experienced the issue with at least two clients: Opera and Wget. They both interpret the response body as a 21-byte string consisting of Connection: close\r\n\r\n. Also, Wget says 200 No headers, assuming HTTP/0.9. Current software versions: Tor 0.1.2.14, Privoxy 3.0.6, Windows XP SP2. I found several mentions of this problem on the web (the first link is the most interesting): http://archives.seul.org/or/talk/Aug-2006/msg00226.html (see caveat #2) http://archives.seul.org/or/talk/Feb-2006/msg00160.html http://photomatt.net/2006/09/11/new-servers/ (see comment by Quix0r) http://framework.zend.com/issues/browse/ZF-1318 (probably misdiagnosed)
Re: HTTP response is Connection: close
On Sun, Jun 24, 2007 at 04:11:51AM -, [EMAIL PROTECTED] wrote 0.9K bytes in 12 lines about: : Sometimes when I perform an HTTP request via Tor, the response is Connection: close rather than the expected content. This happens intermittently, and with various sites. Does anyone know what causes this problem, and whether anything can be done about it? It's been annoying me for quite a while. Most likely, it is a malfunctioning proxy server just beyond the tor exit node. We've seen this when people place squid proxies between their tor exit node and the ISP. The squid proxies malfunction for one reason or another and return Connection: Close. Next time your receive the error, note your exit node. If it consistently causes this problem, you may wish to email the exit node contact. -- Andrew
