- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 13 Jan 2005 17:29:14 +0100
- To: Elias Sinderson <elias@cse.ucsc.edu>
- CC: Mike Lindsey <coyote@gmail.com>, w3c-dist-auth@w3.org
Elias Sinderson wrote: > > Mike Lindsey wrote: > >> [...] My conf output: >> [...] <Location /roam/mike/> >> [...] access_log output for the failed mount: >> [...] 192.138.150.250 - - [12/Jan/2005:22:43:32 +0000] "GET >> /_vti_inf.html HTTP/1.1" 404 346 >> 192.138.150.250 - - [12/Jan/2005:22:43:32 +0000] "POST >> /_vti_bin/shtml.exe/_vti_rpc HTTP/1.1" 404 360 >> 192.138.150.250 - - [12/Jan/2005:22:43:32 +0000] "OPTIONS /roam/mike >> HTTP/1.1" 200 - >> > Please correct me if I'm wrong, but this doesn't appear to be a DAV > issue. Note the differing locations in your DAV configuration > (/roam/mike/) and requests (/_vti_inf.html and > /_vti_bin/shtml.exe/_vti_rpc), where the requests return 404s (Not > Found). Also note that GET and POST won't really test your DAV > configuration, even if pointed at the DAV enabled area of your server. > As your configurations appear identical, you may wish to point your > Sunbird (DAV) client at /roam/mike to see if that works as expected. What we see is Windows trying to connect through Frontpage Server Extensions (which occurs when it thinks there is no WebDAV support). Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 14 January 2005 04:02:40 UTC