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

[Marc Thomas]

Hi Fabian,

I applied your patch below toprivoxy-3.0.26-stable and tested it on the
two sites with this problem.
In both cases it worked. The Web application is now able to make a
tunnel via HTTP CONNECT.

JFYI - One of the proxies is running Squid 2.6.STABLE21. I was not able
to determine what the other one is.


On 07/12/16 11:03, Fabian Keil wrote:
> That's strange behaviour, whether or not the Connection header is set
> shouldn't matter.
Agreed, but it seems some proxies think otherwise.

> There is no option for this but you could try adding:
>    if (csp->http->ssl != 0)
>    {
>       return JB_ERR_OK;
>    }
>
> before the "log_error()" call in parser.c's client_connection_header_adder().
>
> If that doesn't make a difference, a log excerpt that shows the problem
> would be useful.

That does indeed seem to work!

> Note that Privoxy 3.0.21 is severely out of date and contains known
> security issues which your distro may not have backported, as you have
> to recompile Privoxy anyway, you may want to update while your at it.
>
> Fabian

Noted. Many thanks!


Kind Regards,
Marc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-users/attachments/20161207/c17e46f8/attachment.bin>