Menu
▾
▴
[privoxy-users] [ ijbswa-Support Requests-2840156 ] Privoxy prematurely closes connections
|
From: SourceForge.net <no...@so...> - 2009-08-28 15:49:33
|
Support Requests item #2840156, was opened at 2009-08-19 09:26 Message generated for change (Settings changed) made by fabiankeil You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=2840156&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 3.0.x >Status: Pending Priority: 5 Private: No Submitted By: Olivier (poto) Assigned to: Fabian Keil (fabiankeil) Summary: Privoxy prematurely closes connections Initial Comment: Hi I am using Privoxy 3.0.14 to access a proprietary web server (192.168.253.1) running on the same PC (WinXP) as Privoxy, and bound to a TAP-WIN32 interface (192.168.253.2). Privoxy systematically closes prematurely the connection, preventing the browser to retrieve the response data. Attached is a zip file including the corresponding log files: - get1-privoxy.pcap: wireshark traces showing the erroneous http exchange - get1-noproxy.pcap: wireshark traces showing the same http exchange WITHOUT privoxy (nor any proxy). *This works fine*. - privoxy.log: the corresponding Privoxy log messages In this last log, I noticed the weird following messages: Expected content length: 1. Actual content length: 12. Most recently received: 0. Received 12 bytes while expecting 1. Could this be the error cause? When looking at the pcap trace, there is only 1 byte in the response body, how can Privoxy get 12? The TCP FIN message seems to be sent immediately after reading the request headers, hence before any body byte have been read. Thanks for your help ---------------------------------------------------------------------- >Comment By: Fabian Keil (fabiankeil) Date: 2009-08-28 15:49 Message: I think the problem is fixed in jcc.c,v 1.281. It would be great if you could confirm this. ---------------------------------------------------------------------- Comment By: Fabian Keil (fabiankeil) Date: 2009-08-21 20:51 Message: The MSVC project files in CVS are several years out of date and are unlikely to work anyway. They should probably be removed. The recommended (and known to work) method to compile Privoxy is described at: http://config.privoxy.org/user-manual/installation.html#INSTALLATION-SOURCE On Windows one commonly installs the required build tools as cygwin packages. ---------------------------------------------------------------------- Comment By: Olivier (poto) Date: 2009-08-21 09:51 Message: Thanks Fabian In the meanwhile, I'd like to have a try in debugging privoxy to see where could the problem come from (unfortunately I'm in a hurry). I retrieved the sources, and tried to compile/debug with MSVC. But the MSVC project files are for v6, and I have v9 (2008 C++ Express Edition), and the automatic MSVC conversion fails... Do you have any other MSVC project file that I could try ? Otherwise I'll have to recreate the project by hand, but I might make mistakes in the configuration. Thanks ---------------------------------------------------------------------- Comment By: Fabian Keil (fabiankeil) Date: 2009-08-20 21:20 Message: Thanks for the report and the detailed problem description. It looks like Privoxy incorrectly counted parts of the header bytes as belonging to the body. I'm not yet sure why that's happening, but I'll try to look into it next week. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=211118&aid=2840156&group_id=11118 |