privoxy 3.0.20 - connection reset by peer
Sebastian Müller <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi, visiting www.tagesspiegel.de I get the following message in Firefox Connection resetted by peer When I disable the proxy in firefox settings, the page loads immediately. I updated to 3.0.20 after I discovered this failure in 3.0.16 I also tried to disable all actionfile/filterfile options in config by commenting them. The page then starts loading very slowly and the content is broken. Can anyone confirm this? Cheers Sebastian Müller Privoxy log options set debug 1. debug 2 debug 8 debug 32 debug 64 debug 128 debug 256 debug 512 debug 1024 debug 2048 debug 4096 debug 8192 debug 65536 ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Ijbswa-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
logfile.txt
(text/plain, 4.3 KB)
2013-02-14 13:13:46.669 7f79c4cc7700 Connect: Listening for new connections ...
2013-02-14 13:13:46.670 7f79bd255700 Connect: Accepted connection from 10.20.0.117 on socket 5
2013-02-14 13:13:46.672 7f79bd255700 Connect: Complete client request received.
2013-02-14 13:13:46.672 7f79bd255700 Header: scan: GET http://www.tagesspiegel.de/ HTTP/1.1
2013-02-14 13:13:46.673 7f79bd255700 Header: scan: Host: www.tagesspiegel.de
2013-02-14 13:13:46.673 7f79bd255700 Header: scan: User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
2013-02-14 13:13:46.673 7f79bd255700 Header: scan: Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
2013-02-14 13:13:46.673 7f79bd255700 Header: scan: Accept-Language: de-de,de;q=0.8,en-us;q=0.5,en;q=0.3
2013-02-14 13:13:46.674 7f79bd255700 Header: scan: Accept-Encoding: gzip, deflate
2013-02-14 13:13:46.674 7f79bd255700 Header: scan: Cookie: hcfuser=1359631927375785299652; smplu=13596319273762658987; __utma=82136851.435670302.1359631933.1359661435.1359666894.3; __utmz=82136851.1359631933.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); _chartbeat2=gmfw6huqqfxch6nb.1359631934174.1359666896542.00000000000001
2013-02-14 13:13:46.674 7f79bd255700 Header: scan: Connection: keep-alive
2013-02-14 13:13:46.674 7f79bd255700 Header: Keeping the client header 'Connection: keep-alive' around. The server connection will be kept alive if possible.
2013-02-14 13:13:46.675 7f79bd255700 Header: New HTTP Request-Line: GET / HTTP/1.1
2013-02-14 13:13:46.675 7f79bd255700 Actions: +change-x-forwarded-for{block} +client-header-tagger{css-requests} +client-header-tagger{image-requests} +filter{banners-by-link} +filter{webbugs} +filter{unwanted-popups} +hide-from-header{block} +hide-referrer{conditional-block}
2013-02-14 13:13:46.675 7f79bd255700 Request: www.tagesspiegel.de/
2013-02-14 13:13:46.675 7f79bd255700 Connect: to www.tagesspiegel.de
2013-02-14 13:13:46.707 7f79bd255700 Connect: Connected to www.tagesspiegel.de[184.169.79.58]:80.
2013-02-14 13:13:46.707 7f79bd255700 Connect: Created new connection to www.tagesspiegel.de:80 on socket 6.
2013-02-14 13:13:46.707 7f79bd255700 Connect: to www.tagesspiegel.de successful
2013-02-14 13:13:46.728 7f79bd255700 Header: scan: HTTP/1.1 200 OK
2013-02-14 13:13:46.728 7f79bd255700 Header: scan: Server: Apache-Coyote/1.1
2013-02-14 13:13:46.728 7f79bd255700 Header: scan: Content-Type: text/html;charset=utf-8
2013-02-14 13:13:46.728 7f79bd255700 Header: scan: Content-Language: de-DE
2013-02-14 13:13:46.729 7f79bd255700 Header: scan: Vary: Accept-Encoding
2013-02-14 13:13:46.729 7f79bd255700 Header: scan: Content-Encoding: gzip
2013-02-14 13:13:46.729 7f79bd255700 Header: scan: Content-Length: 47629
2013-02-14 13:13:46.729 7f79bd255700 Header: scan: Date: Thu, 14 Feb 2013 11:12:23 GMT
2013-02-14 13:13:46.729 7f79bd255700 Header: scan: X-Varnish: 1076140430 1076139225
2013-02-14 13:13:46.729 7f79bd255700 Header: scan: Age: 0
2013-02-14 13:13:46.730 7f79bd255700 Header: scan: Via: 1.1 varnish
2013-02-14 13:13:46.730 7f79bd255700 Header: scan: X-Cache: HIT webcache001
2013-02-14 13:13:46.730 7f79bd255700 Header: scan: Accept-Ranges: bytes
2013-02-14 13:13:46.730 7f79bd255700 Header: scan: Cache-Control: private, max-age=90
2013-02-14 13:13:46.731 7f79bd255700 Header: scan: Expires: Thu, 14 Feb 2013 11:13:53 GMT
2013-02-14 13:13:46.731 7f79bd255700 Header: scan: x-cdn: Served by WebAcceleration
2013-02-14 13:13:46.731 7f79bd255700 Header: scan: Connection: Keep-Alive
2013-02-14 13:13:46.731 7f79bd255700 Header: Keeping the server header 'Connection: Keep-Alive' around.
2013-02-14 13:13:46.732 7f79bd255700 Header: Adding: Proxy-Connection: keep-alive
2013-02-14 13:13:46.758 7f79bd255700 Error: read from: www.tagesspiegel.de failed: Connection reset by peer
2013-02-14 13:13:46.759 7f79bd255700 Error: Already forwarded the original headers. Unable to tell the client about the problem.
2013-02-14 13:13:46.759 7f79bd255700 Connect: Marking the server socket 6 tainted.
2013-02-14 13:13:46.759 7f79bd255700 Connect: Closing server socket 6 connected to www.tagesspiegel.de. Keep-alive: 1. Tainted: 1. Socket alive: 0. Timeout: 20. Configuration file change detected: 0
2013-02-14 13:13:46.759 7f79bd255700 Connect: Closing client socket 5. Keep-alive: 1. Socket alive: 1. Data available: 0. Configuration file change detected: 0. Requests received: 1.