RE: httpd accelerator and PURGE command (2.2STABLE5)

Um,

just checked doing just a simple

$ telnet revproxy 80
PURGE http://www.site.uk/dir/file.html HTTP/1.0

Anyway with the
httpd_accel_with_proxy
option turned off (as is default) it returns an error

Access control configuration prevents your request from
begin allowed at this time....

However, with the httpd_accel_with_proxy option turned on, it works.

I'll check RFC 2616 but can you tell me why the option is available if it
should not be used. More so, why is the default in contravention of the RFC?

Thanks for your help!

--
Michael Miller                  michael@oyster.co.uk 
Unix Systems Administrator      +44 20 7446 7484
Oyster Partners Ltd
> -----Original Message-----
> From: Henrik Nordstrom [mailto:hno@hem.passagen.se]
> Sent: 13 December 1999 20:15
> To: Michael Miller
> Cc: 'squid-users@ircache.net'
> Subject: Re: httpd accelerator and PURGE command (2.2STABLE5)
> 
> 
> Michael Miller wrote:
> 
> > Does anyone else think that with the appropriate ACLs in 
> place, you should
> > be able to use the PURGE command without the need for the option
> >     httpd_accel_with_proxy
> > to be turned on?
> 
> Yes, issue a non-proxy PURGE request. This will slip by the accel-only
> checks.
> 
> PURGE /path/to/file HTTP/1.0
> 
> 
> By the way, running a accelerator withour httpd_accel_with_proxy is
> stricly speaking non-compliant with RFC 2616.
> 
> --
> Henrik Nordstrom
> Squid hacker
>