[squid-dev] [PATCH] risky_server_pconn_reuse option
Eduard Bagdasaryan
eduard.bagdasaryan at measurement-factory.com
Tue Mar 8 12:30:38 UTC 2016
Followed your suggestions in [t4] patch.
Eduard.
2016-03-07 17:20 GMT+03:00 Amos Jeffries <squid3 at treenet.co.nz>:
> * To fit with the rest of the directives this should be called
> server_pconn_for_nonretriable.
>
> * This is not a RFC violation, so you dont need to wrap any of its code
> in USE_HTTP_VIOLATIONS.
> The current Squid behaviour was just a hack Alex added years back to
> prevent the old behaviour this is trying to selectively re-enable now.
> Since it was causing so many client-visible error messages when we first
> moved to HTTP/1.1 defaults.
>
> * What the risk is should probaly be noted in the documentation; That
> the requests it enables to re-use pconn can result in 500 errors
> reaching clients/users eyes if there are any network delivery issues, or
> the server closes its connection while the request is still bufferd
by TCP.
>
> * only indent cf.data.pre text with 1 tab, not 2.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-dev/attachments/20160308/9627f4d1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SQUID-93-risky-server-pconn-reuse-t4.patch
Type: text/x-patch
Size: 9928 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-dev/attachments/20160308/9627f4d1/attachment.bin>
More information about the squid-dev
mailing list