[Privoxy-users] Privoxy sending "Connection: close" after CONNECT method causes some upstream proxies to drop the connection.

[Marc Thomas]

Hi Ian,

Thanks for the quick reply. I compiled Privoxy 3.0.26-stable from
source, and the issue is still present.
I put Privoxy into debug level 13327 and it can be seen adding the
"Connection: close" in the log file, for example:

2016-12-07 10:25:20.277 7f9bb1531700 Header: Adding: Connection: close

I also took a network trace just to confirm it is also being sent on the
wire.


Here's a bit more context around that log entry:

2016-12-07 10:25:10.833 7f9bb2b60700 Info: Privoxy version 3.0.26
2016-12-07 10:25:10.834 7f9bb2b60700 Info: Program name:
/opt/xxxxXX/yyyyyyy/privoxy/privoxy
2016-12-07 10:25:10.834 7f9bb2b60700 Info: Loading filter file:
/opt/xxxx/yyyyyyy/privoxy/default.filter
2016-12-07 10:25:10.836 7f9bb2b60700 Info: Loading filter file:
/opt/xxxx/yyyyyyy/privoxy/user.filter
2016-12-07 10:25:10.836 7f9bb2b60700 Info: Loading actions file:
/opt/xxxx/yyyyyyy/privoxy/match-all.action
2016-12-07 10:25:10.836 7f9bb2b60700 Info: Loading actions file:
/opt/xxxx/yyyyyyy/privoxy/default.action
2016-12-07 10:25:10.840 7f9bb2b60700 Info: Loading actions file:
/opt/xxxx/yyyyyyy/privoxy/user.action
2016-12-07 10:25:10.840 7f9bb2b60700 Info: Loading trust file:
/opt/xxxx/yyyyyyy/privoxy/trust
2016-12-07 10:25:10.840 7f9bb2b60700 Connect: Initialized 100 socket slots.
2016-12-07 10:25:10.840 7f9bb2b60700 Info: Listening on port 8118 on IP
address 0.0.0.0
2016-12-07 10:25:10.840 7f9bb2b60700 Connect: Waiting for the next
client connection. Currently active threads: 0
2016-12-07 10:25:20.003 7f9bb2b60700 Connect: Waiting for the next
client connection. Currently active threads: 1
2016-12-07 10:25:20.003 7f9bb1531700 Connect: Accepted connection from
127.0.0.1 on socket 5
2016-12-07 10:25:20.004 7f9bb1531700 Header: scan: CONNECT
zzz07.vvv.com:443 HTTP/1.1
2016-12-07 10:25:20.005 7f9bb1531700 Header: scan: Proxy-Connection:
Keep-Alive
2016-12-07 10:25:20.005 7f9bb1531700 Header: crumble crunched:
Proxy-Connection: Keep-Alive!
2016-12-07 10:25:20.005 7f9bb1531700 Header: addh-unique: Host:
zzz07.vvv.com:443
2016-12-07 10:25:20.005 7f9bb1531700 Header: Adding: Connection: close
2016-12-07 10:25:20.005 7f9bb1531700 Request: zzz07.vvv.com:443/
2016-12-07 10:25:20.006 7f9bb1531700 Connect: via [192.168.1.4]:3129 to:
zzz07.vvv.com:443
2016-12-07 10:25:20.006 7f9bb1531700 Connect: Connected to
192.168.1.4[192.168.1.4]:3129.
2016-12-07 10:25:20.006 7f9bb1531700 Connect: Created new connection to
zzz07.vvv.com:443 on socket 6.
2016-12-07 10:25:20.006 7f9bb1531700 Connect: to zzz07.vvv.com:443
successful
2016-12-07 10:25:20.274 7f9bb1531700 Connect: Closing server socket 6
connected to zzz07.vvv.com. Keep-alive 0. Tainted: 1. Socket alive 1.
Timeout: 0.
2016-12-07 10:25:20.275 7f9bb1531700 Connect: Closing client socket 5.
Keep-alive: 0. Socket alive: 0. Data available: 0. Configuration file
change detected: 0. Requests received: 1.


Any suggestions how to suppress adding the "Connection: close"?

Thanks & Kind Regards,
Marc


On 06/12/16 16:26, Ian Silvester wrote:
> Hi Marc,
>
> I can't seem to find the specific changelog item, but I believe this is
> a bug that was fixed in a release subsequent to the version you're
> using. Please try compiling from the most recent source available at
> Sourceforge (or at the project's own web site).
>
> Cheers,
>
> Ian
>
>
> My PGP public
> key[http://diem.serveftp.net:8080/IanSilvesterPGPPublicKey.asc]