Hello Dave,
in my personal Top Ten of 'Most Broken WebDAV Servers' and 'Don't Give a
Damn on Standards and Interoperability' box.net is number one.
It does not work with davfs2 either. Here are some more bugs:
- In response to OPTIONS it includes header 'DAV: 1,2', but does not
support locks.
- A HEAD-request on a nonexisting resource is answered with '200 OK'.
- Time stamps seem to be chosen randomly. An example from a test with
litmus:
PUT /dav/litmus/res HTTP/1.1
.
HTTP/1.1 201 Created
Date: Thu, 12 Jul 2007 09:23:16 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
GET /dav/litmus/res HTTP/1.1
.
HTTP/1.1 200 OK
Date: Thu, 12 Jul 2007 09:27:27 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Last-Modified: Thu, 12 Jul 2007 09:29:49 GMT
Maybe they want to prevent clients from caching.
- It uses Basic authentication over insecure connections, violating RFC
4918, 20.1.
Unfortunately many WebDAV-servers do this. Probably we should warn
users more about this.
You wrote:
Mon Jul 9 17:09:27 PDT 2007:
> I've asked them for info to try and track down the bug on the server
> side
Tue Jul 10 15:40:53 PDT 2007:
> They wrote back to say that they're currently not planning on adding
> WebDAV to their services,
That's funny. They use WebDAV-methods defined in RFC 4918, send header
'DAV: 1,2' and are 'currently not planning on adding WebDAV to their
services'. I would be interested to read the full text of their answer.
Cheers
Werner
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
