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

Thanks Amos for this information

Regards,
Saurabh

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Thursday, September 18, 2008 3:13 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
>
> Is there a stable build in SQUID 3.0 for which the design flaw around
> extension methods has been fixed? Has someone tested this fix in 3.0?

No. Just minor bug fixes to how the logs display of them.

>
> Also when can I expect SQUID 3.1 to get stable?

3.1 PRE is due out early October. We expect a STABLE within 4-8 weeks,
though the exact timing of that depends on an absence of major bugs in
the PRE.

Most of the testers so far have not found anything major so the HEAD
snapshots can be considered usable now and very nearly feature-complete
to what 3.1 will be.

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.STABLE4 or 3.0.STABLE9