[squid-dev] [PATCH] adapting 100-Continue / A Bug 4067 fix

[Marcus Kool]

On 11/01/2014 03:59 PM, Tsantilas Christos wrote:
> Hi all,
>
> This patch is a fix for bug 4067:
>      http://bugs.squid-cache.org/show_bug.cgi?id=4067

The bug report has a list of bugs.  Which ones are addressed ?

Thanks
Marcus

> Currently squid fails to handle correctly "100 Continue" requests/responses  when adaptation/ICAP  is used. When a data-upload request enters squid (eg a PUT request with  "Expect: 100-continue"
> header), squid sends ICAP headers and HTTP headers to ICAP server and stuck waiting for ever  the request body data.
>
> This patch implements the "force_request_body_continuation" access list  directive which controls how Squid handles data upload requests from HTTP and send the request body to Squid.
 >
> An allow match tells Squid to respond with the HTTP 100 or FTP 150 (Please Continue) control message on its own, before forwarding the request to an adaptation service or peer. Such a response usually
> forces the request sender to proceed with sending the body. A deny match tells Squid to delay that control response until the origin server confirms that the request body is needed. Delaying is the
> default behavior.
>
> This is a Measurement Factory project
>
>
> _______________________________________________
> squid-dev mailing list
> squid-dev at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-dev
>