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

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/11/2014 6:59 a.m., Tsantilas Christos wrote:
> Hi all,
> 
> This patch is a fix for bug 4067: 
> http://bugs.squid-cache.org/show_bug.cgi?id=4067
> 
> 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
> 

Sorry its taken so long. The patch looks fine, but will need a rebase
and re-audit on top of parser-ng changes that just landed in trunk.

Amos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUXIizAAoJELJo5wb/XPRjONUH/3D6jRYleA7FrjbylZhZlJEF
LuirY4YtJtgIJSL0Vqn/6IzSQaRLBds1X4hEdGMNJJU3WftvwRLQ8vEpM6MPadDb
gQ5aPJVkRYMRg56t/ZjxVA+oLJyb5J3kASdg2zE9LPJjRSq14lcQ+vCdOve7ceDY
nin/1hTC9Yl6LFyoLC0oQGcaBv6X9vGOXDQ74v1MCSo6Rt3m83UnqjNtSLDt1sOl
W3WLTyuEQwlc+c1Pz58bqnq1CY/wYebEET8rSIIV3rH/ohdDKV+HHb5NDRhnDeVa
eZkecsRuIdTc3LS3vSzZC9MNvSE310AsjY8+G9no5G5o61U0n90lROH/yh1m8rE=
=/UQi
-----END PGP SIGNATURE-----