- From: Jim Davis <jdavis@parc.xerox.com>
- Date: 1999年2月16日 10:29:57 PST
- To: Dana Carson <dcarson@toad.net>, WEBDAV WG <w3c-dist-auth@w3.org>
- Message-Id: <3.0.5.32.19990216102957.00986420@mailback.parc.xerox.com>
At 03:15 AM 2/16/99 PST, Dana Carson wrote: > >Arugh. Fixed. Yes, fixed. My test script got further, but then hit the following bug PROPFIND /jrd/foo.html HTTP/1.1 Host: www.fwi.com Authorization: Basic anJkOmZvbw== content-length: 105 content-type: text/xml <?xml version="1.0"?> <A:propfind xmlns:A="DAV:"> <A:prop><A:getcontenttype/></A:prop> </A:propfind> HTTP/1.1 207 Multi-Status Date: 1999年2月16日 18:26:23 GMT Server: Apache/1.3.3 (Unix) WSD/DAV 0.5.15 Content-Length: 298 Content-Type: text/xml <?xml version="1.0" ?> <D:multistatus xmlns:D="DAV:" xmlns:W="http://www.cyberteams.com/"> <D:response> <D:href>http://serv1-r.fwi.com/jrd/foo.html</D:href> <D:propstat> <D:prop> <getcontenttype/> </D:prop> <D:status>HTTP/1.1 400 Bad Request</D:status></D:propstat> </D:response> </D:multistatus> 1) I think this is a valid request. (I could be wrong). Why does mod_webdav reject it? 2) If it does indeed think it's an invalid request, it should return status 400, not 207 Multistatus, because the error applies to the entire request as a whole, not to the status of some individual resource within a set.
Received on Tuesday, 16 February 1999 13:30:11 UTC