feat: add partial update support

[janlay]

Summary

Adds partial update support for WebDAV clients that require range-based writes, especially webdavfs.

This includes support for:

• PATCH with X-Update-Range
• PUT with Content-Range
• advertising sabredav-partialupdate via the DAV response header
• exposing Accept-Patch: application/x-sabredav-partialupdate

Motivation

Some WebDAV clients, such as miquels/webdavfs, probe for PUT range support before mounting read-write. Without partial update support, they fall back to read-only mode with:

no PUT Range support, mounting read-only

Advertising and implementing SabreDAV-style partial updates allows these clients to mount read-write.

Changes

• Intercept OPTIONS to advertise partial update capability.
• Handle partial updates before delegating to golang.org/x/net/webdav.
• Add PATCH permission handling equivalent to PUT.
• Add CORS defaults for PATCH, Content-Range, and X-Update-Range.
• Add tests for:
  • OPTIONS partial update headers
  • PATCH partial writes
  • sparse partial file creation
  • PUT with Content-Range

Testing

go test ./...
go build -o webdav .

Also manually verified with webdavfs on Debian:

sudo mount -t webdavfs -o"username=user,password=pass,allow_other,rw" http://10.0.0.2:6065 /mnt/test

The mount succeeds as read-write and no longer reports missing PUT range support. A mounted-file partial overwrite test also passed.

[hacdias]

Hi @janlay! Could you open this PR to add the partial update support on the upstream library: https://cs.opensource.google/go/x/net/+/master:webdav/?

[janlay]

Hi @hacdias, this repo is more application-oriented than the official one, making it easier to implement; whereas that repo implementation is very low level and requires quite a long time. I’m trying to build on the existing code in that repo and achieve partial update capability with as few changes as possible. And I can’t estimate how long it will take to complete.

So, I hope to merge it here first, so that users can enjoy the full-featured WebDAV server. In the future, if the improvements are accepted in the official repo, then we can simplify this here.