It would be really helpful if anybody who has used WebDav can actually share their experience on what worked and what didn't work for them?
WebDAV provides a foundation that many things are built on. As others have noted there is CalDAV and CardDAV that many use all the time.
But, it goes beyond that. WebDAV has many of the features we regularly use in object storage. Yet, object storage provides often have their own proprietary API or clone someone elses proprietary API. WebDAV is an open spec.
Because WebDAV has been around for so long, there are integration's with just so many things which make it easy to get something going out of the gate. For example, all the major OS support working with it.
Not only is it relevant for this but with all the discussions on reviving more of the open web... this is a piece worth looking at.
Oh - hell - yes, and Microsoft IIS. That was a big user back in the day, again for FrontPage integration, but you could use it generically too
And of course, Windows and OS X still support mounting WebDAV URLs as drives.
edit: it ain't going anywhere: https://www.ics.uci.edu/~ejw/authoring/implementation.html
and the tomcat module https://wiki.apache.org/tomcat/Tomcat/WebDav
however, each and almost every of them speak its own dialect, so client compatibility will be spotty.
It's actually pretty neat.
As of Windows 10, Microsoft has even phased out cmd.exe from the menus and for shortcuts like Win+X. It's still possible to get the legacy environment back, but it's exactly that: a legacy environment.
I also once integrated an open-source WebDAV server into my own code, in order to expose parts of an SQL database as a remotely mountable filesystem. This would have taken much more effort without the existing WebDAV infrastructure.
The core and mail specifications are where the focus is, and they’re what’s currently approaching standardisation in the IETF, but there are also the calendar and contact specifications in progress, which are designed to replace CalDAV and CardDAV. I don’t think they’re getting a great deal of attention now, while core and mail are finalised, but once those are done I expect more attention will come to them. (In the mean time, I believe we’ll be speaking the calendar and contact JMAP drafts in FastMail when we switch over to JMAP.)
The ability to do everything over one protocol instead of at least four—IMAP, SMTP, CalDAV and CardDAV—is one of the nice things about JMAP.
CalDAV and CardDAV are certainly alive, but I think they're in a pretty horrible place.
I run a Radicale server, which seems very nice, but configuring clients is a nightmare. Every client seems to require different settings, and work to differing degrees.
The native Contacts/Calendar apps on OS X were the worst. They connect, work for a few hours or days, and then permanently break. I have to delete and re-add the accounts over and over again until eventually the same settings suddenly work, and they work for some hours or days, and then break again.
Thunderbird consistently works, as does Android's DAVdroid, but other clients I've tried have been almost-hit-or-completely-miss.
emacs –– EMACS –– has terrible support. This might not sounds like much, what with it being a text editor and all, but this is exactly the sort of place where it usually has 15 different implementations, 2 or 3 of which are really nice. Instead, it's riddled with XML parsing errors, the biggest CalDAV client deletes all of your TODO entries, and there doesn't seem to be a single CardDAV library. I take this as a sign that those protocols are not being widely embraced.
That said, when they work they are truly fantastic. I don't particularly care about the underlying protocol, but I pray that CalDAV and CardDAV support gets more consistent and more popular.
I use Apache2 + SQLite for the authentication, here is an example configuration: https://gist.github.com/aurorabbit/36c509ddeeba2b97c3019534f...
I use buildroot for creating a minimal linux install.
Also provides vault URLs so you can use third-party clients if need be on a local (and configurable) port.
It's unreliable; a tangle of half-implemented standards and incompatible clients, and it's uninteresting as a file system that lacks basic features, like locking, server-side search, etc...
Tried again recently, Windows 10 with latest apache webserver fails hard on simple tests.
Some technologies must just die and disappear.
It had a lot of promise, but very poor actual implementation. I'd still like to see a generalized, cross-platform replacement for SMB/NFS/CIFS.
I also compile it for other reasons, including getting the latest version and applying all the libc hardening options and using the latest pcre. I do this for about a dozen internet facing daemons. It takes about 9 minutes for all my packages to compile.
Ever since I saw eCos OS, I wanted every OS to come with both the ability and a GUI tool to just check off all the features I want, compile kernel with just those features, and create installer for that kernel. Current tech in repos should even let one create that configuration automatically based on what packages they wanted or have already installed in a sample system (eg bare metal or VM). Could also use program analysis where features are dropped if they're not called and/or info from security policies like SELinux for further constraints.
Have you ever tried to properly set up samba or NFS in a container?
Usually if you have a desktop/mobile application that has a self hosted setup they are using WebDAV.
It is done and finished.
Webdav was mostly used to provide "easy" access to webdevelopers where at time were using IDEs for Flash (Macromedia) and HTML (Frontpage).
Once they finished from the IDE they upload the files.
But webdav is a mess to setup (servers and permissions) and was deprecated to better protocols (ssh, scp).