If adding patches...I would suggest keeping up with the common
non-standard methods, hard-coded in. If we know what they are well
enough to note them in the conf, might as well put them in the list all
the time. They can be disallowed via ACL if someone hates WebDAV.
Duane Wessels wrote:
>
>
> On Wed, 27 Mar 2002, Adrian Chadd wrote:
>
>
>>Hi guys,
>>
>>I'd like to propose that we have a config file entry for extension_Methods
>>which lists all of the 'common' methods.
>>
>>eg this one, and all of the evil webdav stuff.
>>
>
> AFAIK, all known webdav methods (even the nonstandard ones) are
> already hard coded. Are you proposing something as simple as this?:
>
> Index: cf.data.pre
> ===================================================================
> RCS file: /squid/squid/src/cf.data.pre,v
> retrieving revision 1.199.2.7
> diff -u -3 -p -u -r1.199.2.7 cf.data.pre
> --- cf.data.pre 2001/04/04 07:01:12 1.199.2.7
> +++ cf.data.pre 2002/03/27 16:31:09
> @@ -3281,6 +3281,11 @@ DEFAULT: none
> DOC_START
> Squid only knows about standardized HTTP request methods.
> You can add up to 20 additional "extension" methods here.
> +
> + For example, you may want to add the following methods:
> + GNUTELLA
> + BLAH
> + ...
> DOC_END
>
> NAME: high_response_time_warning
>
>
>
>
>
-- Joe Cooper <joe@swelltech.com> http://www.swelltech.com Web Caching Appliances and SupportReceived on Wed Mar 27 2002 - 13:07:03 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:54 MST