From: Hungerburg <pc...@my...> - 2010-09-27 12:29:43
|
Am 2010-09-27 10:04, schrieb Dannes Wessels: >> Using Natulius as file manager, I get a HTTP not found error when I >> try to access eXist with >> >> dav://admin@localhost:8080/exist/webdav/db/ >> > > I can confirm, In the logging I see some typical logging..... > > dav://admin@localhost:8080/exist/webdav/db/foo/bar/ > dav://admin@localhost:8080/exist/webdav/db/foo/ > dav://admin@localhost:8080/exist/webdav/db/ > dav://admin@localhost:8080/exist/webdav/ > > and for the last PROPFIND does not work..... this seems to stop Nautilus to > work.... > > will check...... hello Dannes, the same happens with the *Bitkinex* webdav client. It gets stuck in an (endless) loop as it tries to "GET /exist/webdav HTTP/1.1". The app displays the headers of the chat nicely in a gui. if I correctly parse http://www.webdav.org/specs/rfc4918.html#collection.resources, quote: > Clients MUST be able to support the case where WebDAV resources are contained inside non-WebDAV resources. For example, if an OPTIONS response from "http://example.com/servlet/dav/collection" indicates WebDAV support, the client cannot assume that "http://example.com/servlet/dav/" or its parent necessarily are WebDAV collections. So, clients are allowed to test, if the parent is a webdav resource. Maybe they are wrong to interpret a 404 on the parent to imply that the full url isnt valid too. BUT maybe if the GET or OPTIONS returned 204 instead of 404 in that case, they would just start to work? Would you give it a try? Regards -- peter |