Re: cache.log error messages, please help!

Trust us. It really is rather definite. If you look at the IE5
'webfolders' stuff, you'll find that it's implementing what amounts to a
network filesystem over HTTP/1.1.

Out of curiosity, I picked up, complied and installed the webdav apache
module and ran some tests. It's pretty agressively HTTP/1.1 (that is, if
you downgrade the advertised protocol, it won't talk to you). _PROBABLY_
it would be possible to wedge in support by making some extra methods
that are essentially copies of POST, and then forcing the HTTP version
to remain at 1.1, but it's not something I'd attempt without a safety
harness, myself.

As for the URL string, I fear that the paths are just regular paths
(from what I've seen). It's the methods and headers that are the key.

Of course you _can_ use methods in ACL's....but the whole thing looks a
little fraught.

D

Chris Pickert wrote:
>
> Thanks for the response. And I'm wondering, where'd you find this "definite"
> <grin> answer? I surfed around for at least an hour but, no luck. And when
> you say that in transparent proxy there's no way around this. Does this
> issue deal with the cacheing of the request object or is the problem
> otherwise incompatabile. I was thinking if you could get a "generic" url
> string that is present in these request that you could disable the caching
> of the object by putttting the string in heirarchy_stoplist and the no_cache
> ACL. Post or email what you think. thanks.
>
> - peace, chris
> ==] Christopher Pickert (cpickert@worldinter.net)
> ==] System / Network Analysist & UNIX Technician
> ==] WorldInternet, Corp. [http://www.worldinter.net]
> ==] (877) 648-8400 - x166 - (Network Operations Center)
>
> Henrik Nordstrom wrote:
>
> > Chris Pickert wrote:
> >
> > > 1999/06/07 06:48:18| clientReadRequest: FD 59 Invalid Request
> > > 1999/06/07 08:19:21| clientReadRequest: FD 106 Invalid Request
> > > 1999/06/07 08:22:31| clientReadRequest: FD 101 Invalid Request
> > > 1999/06/07 09:31:03| clientReadRequest: FD 138 Invalid Request
> > > 1999/06/07 11:18:26| parseHttpRequest: Unsupported method 'PROPFIND'
> > > 1999/06/06 23:01:00| parseHttpRequest: Unsupported method 'OPTIONS'
> > >
> > > I read around on nlanr but couldn't get a definite answer.
> >
> > The definite answer is:
> >
> > WebDAV (rfc2518) is not yet supported by Squid, and makes Squid rather
> > confused when used.
> >
> > One "hidden" WebDAV client used by many users is Microsoft Outlook
> > talking to "Internet" (HotMail and others) mail servers.
> >
> > Until support is ready in Squid any WebDAV clients should not be
> > proxied. In the case of Microsoft Outlook it apparently copies any proxy
> > settings from IE when installed, and this has to be manually removed. If
> > you are doing transparent proxying then there is not much you can do.
> >
> > --
> > Henrik Nordstrom
> > Spare time Squid hacker
Received on Tue Jun 08 1999 - 02:22:59 MDT