[squid-dev] [PATCH] Temporary fix to restore compatibility with Amazon

[Eliezer Croitoru]

About the shaming idea:
I do not like in any way and time to write bad things on anyone.
To make sure there is a bug and to make sure where the bug is from I 
would try to first understand the bug and maybe someone would be able to 
make this world a better place for programs and programmeres.

I will not run to triage this issue for now but the last idea of amos 
seems to me pretty reasonable(reading the description and not the code).

Eliezer

On 24/06/2015 08:55, Alex Rousskov wrote:
> Hello,
>
>      This temporary trunk fix adds support for request URIs containing
> '|' characters. Such URIs are used by popular Amazon product (and
> probably other) sites: /images/I/ID1._RC|ID2.js,ID3.js,ID4.js_.js
>
> Without this fix, all requests for affected URIs timeout while Squid
> waits for the end of request headers it has already received(*).
>
>
> The proper long-term fix is to allow any character in URI as long as we
> can reliably parse the request line (and, later, URI components). There
> is no point in hurting users by rejecting requests while slowly
> accumulating the list of benign characters used by web sites but
> prohibited by some RFC.
>
>
> HTH,
>
> Alex.
> P.S. (*) which is probably another parsing regression bug (not addressed
> by this temporary patch or the long-term fix discussed above), but I
> have not tested whether the very latest trunk still suffers from this
> other bug.
>
>
>
> _______________________________________________
> squid-dev mailing list
> squid-dev at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-dev
>