RE: [squid-users] why does squid have extension_methods to be configurable?

Hi All

Can someone tell if the extension_methods default blocked behavior been fixed in 3.1 release? Also is it fixed in 2.7 release?

Please let me know if someone has tested it successfully.

Regards,
Saurabh

-----Original Message-----
From: Saurabh Agarwal
Sent: Friday, July 18, 2008 11:34 AM
To: Amos Jeffries
Cc: squid-users_at_squid-cache.org
Subject: RE: [squid-users] why does squid have extension_methods to be configurable?

Good to know this. Thanks Amos

Regards,
Saurabh

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Thursday, July 17, 2008 6:25 PM
To: Saurabh Agarwal
Cc: squid-users_at_squid-cache.org
Subject: Re: [squid-users] why does squid have extension_methods to be
configurable?

Saurabh Agarwal wrote:
> Hi All
>
> By Default Squid supports only Standard HTTP request methods. For
Squid
> to support non-standard HTTP methods we need to add them explicitly in
> squid.conf file for SQUID to allow these requests. Why does SQUID
blocks
> the unknown HTTP methods and why it doesn't just pass them on?

Squid was designed very early in the life of the Internet. There were no

extensions way, way back then.
We have corrected this design flaw in 3.1.

>
> Is there a way we can configure SQUID to allow HTTP extension methods
in
> one go?

Not with code alteration. Someone has submitted a patch to do this for
2.x today.

Amos

-- 
Please use Squid 2.7.STABLE3 or 3.0.STABLE7