On Mon, 1 Feb 2010 17:10:47 +0530, Saurabh Agarwal <Saurabh.Agarwal@xxxxxxxxxx> wrote: > 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? As per the email you quoted: "We have corrected this design flaw in 3.1." It has also been resolved in Squid-2.HEAD (alpha code for 2.8 release). But not in the official 2.7 releases. > > Please let me know if someone has tested it successfully. Many people are using it regularly now. Amos > > Regards, > Saurabh > > -----Original Message----- > From: Saurabh Agarwal > Sent: Friday, July 18, 2008 11:34 AM > To: Amos Jeffries > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: RE: why does squid have extension_methods to be > configurable? > > Good to know this. Thanks Amos > > Regards, > Saurabh > > -----Original Message----- > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Thursday, July 17, 2008 6:25 PM > To: Saurabh Agarwal > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: Re: 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
