[squid-users] Modelling behaviour of old version of squid with the latest using rules ?

[Amos Jeffries]

On 18/02/2016 8:51 a.m., Mike Corlett wrote:
> Hi all,
> 
> I recently went to demo a website on a company site that used an old
> version of squid ( think 2.x ), so that all the PATCH posts to our website
> from a browser were turned into METHOD_OTHER, which broke the website for
> us and nothing worked.
> I want to be able to recreate this rule so we can build an in-house squid
> server to test against things like this, and just wondered if I can map
> REQUEST types to simulate this behaviour. Therefore we can tweak our
> website to work with older versions of squid.
> 
> Obviously I could just download and install an old version of squid, but
> this would then mean I suffer the security problems associated with old
> versions !, so wondered if this one rule could be modelled. So far I've
> worked out how to totally block PATCH requests, but that's not really good
> enough.


An ICAP service or eCAP module can alter any part of the message. So it
should be easy for one of those to re-write the request method from
anything outside the small RFC 2068/2616 set to be "METHOD_OTHER".

Amos