From: Hungerburg <pc...@my...> - 2010-09-27 21:58:17
|
Am 2010-09-27 14:29, schrieb Hungerburg: > 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? I made a proxy to test my own case: $ mknod response p $ nc -4 -l localhost 8081 0<response | tee client.log | nc -4 server 8080 | sed -u -e 's:HTTP/1.1 404 Not Found:HTTP/1.1 204 No Content:' | tee server.log 1>response $ mount -t davfs http://localhost:8081/exist/webdav/db/ SOME_DIR now it fails with: Not a WebDAV enabled share. Then I learned that pure gvfs (the engine behind nautilus webdav?) actually ignores the 404 on /exist (without /db), and can also be configured to display rich debugging output: $ GVFS_HTTP_DEBUG=all /usr/lib/gvfs/gvfsd -r $ gvfs-mount dav://server:8080/exist/webdav/db $ ls ~/.gvfs/WebDAV on server/ with this webdav implementation files cannot be created and xml documents are empty. its a mess. Please keep going. -- peter |