Re:Many Hells of WebDAV: Writing a Client/Server in Go
by kayo_20211030 on Wednesday January 07, 2026 @11:19AM
(#46528206)
I honestly didn't know WevDAV was still a thing. It seems like a nightmare from which we should have woken up long ago. I do sympathize though. Every service implements (or implemented) it differently, or spottily, or partially. Is it another example of the adage that "even your bugs have users"?
[ Parent
| on HN ]
Re:Many Hells of WebDAV: Writing a Client/Server in Go
by calvinmorrison on Wednesday January 07, 2026 @12:20PM
(#46529222)
WebDav, life before S3
Re:Many Hells of WebDAV: Writing a Client/Server in Go
by kayo_20211030 on Wednesday January 07, 2026 @12:36PM
(#46529462)
lol. "Life, Jim, but not as we know it."
Re:Many Hells of WebDAV: Writing a Client/Server in Go
by willhschmid on Thursday January 08, 2026 @12:18PM
(#46543612)
Why is it a nightmare? I use WebDAV almost every day. All my online servers support it, and it makes it super easy for me to map them as a file system driver in Windows, allowing me to edit files directly on the server.
Re:Many Hells of WebDAV: Writing a Client/Server in Go
by kayo_20211030 on Saturday January 10, 2026 @09:46AM
(#46566125)
Using WebDAV is generally fine, if you have the tools. The weirdness (the hell?) is when you're required to write those tools, or libraries yourself; most especially when the tools you'll write need to work with different flavors of servers. Each's adherence to the protocol is a little "loose" at times. Odd responses. Odd errors. The whole gamut. When it works, it works fine; when it doesn't it really is a bit of a nightmare.