4 ms·
We implemented WebDAV (rust/actix-web) for our product and it's great that you can mount it as a mostly native file system on all major OSes, but there are a lo
by cetra3 8y ago
We implemented WebDAV (rust/actix-web) for our product and it's great that you can mount it as a mostly native file system on all major OSes, but there are a lot of issues with Implementation:
* Windows sometimes appends a `/` at the end and sometimes doesn't when looking for folders, so you better make sure you return the same results for either.
* Windows WebClient service is buggy as hell. You have no event logs (that I could find) to find out what's wrong and end up restarting the service continuously. this includes if you get your username/password wrong, if there is an interrupt to the server (i.e, wifi drops), etc.. Wireshark is your friend, but it won't tell you why it's not working.
* Forget about Basic Auth on windows, credentials are not persisted across reboots/logouts, and you need to adjust registry to support non-ssl sites at all. Using Kerberos is really your only option, but if you want to use it on non .local domains, then you need to add in a registry key to allow this, as windows assumes that only .local domains would use SSO.
* Last time I checked, Adobe Lightroom won't even save to a WebDAV drive on OSX as it thinks there is no space.
* Lots and lots of noisy connections on both windows and OSX that aren't really needed, but happen anyway. Don't get me started on the amount of temp files that are saved/used, and don't filter them out either as things start breaking like Photoshop and folder uploads.
* Weird error messages that don't give you an idea of what's going on. Error code 100000041? Oh yeah I know what that one is!
* URL size limitations in Windows, make sure your entire path isn't too long!
All in all I am glad we have WebDAV for native-like access, but it is a massive pain to deal with some of the niggly bits between implementations.