Oh WebDAV, the protocol I loved and hated the last 20 or so years... - There were proprietary implementations NetDrive and rebranded as WebDrive for winNT whic

Oh WebDAV, the protocol I loved and hated the last 20 or so years... - There were proprietary implementations NetDrive and rebranded as WebDrive for winNT which set up a WebDAV mount as a drive letter. Worked nicely for code editing in a CMS but completely corrupt files once in a while. Unless you had a SMP machine, then it would regularly blue screen - WinXp had the first native ‘NET USE’ support I think. It was built on top of the HTTP support in the OS but didn’t persist state properly, so if you didn’t know to disable automatic proxy detection in your internet options, every WebDAV action would take 2 seconds to do a proxy detect, ruining the experience. - Actually getting WebDAV to work was hit or miss. It helped to specify the password on the command line to NET USE for some reason - office supported WebDAV too, and depending on its mood would either treat a WebDAV drive letter as just a drive, or speak WebDAV natively - I’m pretty sure the initial Vista release completely broke WebDAV. Never got it to work properly. Sad given that MS was supposed to be invested in this standard - Getting it to work safely on OSX was another challenge, as OSX heavily caches content client side and if the server side content changed, either remount to see the changes or write a tool to send a poorly defined control command to WebDAV to flush the cache. At one point we automated the server to inform a local tool on the macs to do this flushing - oh, and automating mount_webdav to log you in requires speaking some property protocol over a fd to the application. Which broke at around OS X 10.10. Got to learn my way around the WebDAV implementation in Darwin back then to figure out both this and the cache flushing. Thank apple for at least publishing the source to this Well, fortunately I don’t need WebDAV as much anymore as I have in the past.