As of PR #21 (later than version 1.1) WebDAV Daemon will report itself as compliance levels 1 and 2 instead of just 1. As far as I'm aware it is not compliant with class 2.
The move to report compliance without actually supporting it correctly was a pragmatic decision to get some clients to interact with the server (see #17 ).
Before the next release this must be fixed. According to RFC 4918 compliance class 2 requires the server MUST:
And SHOULD also support the
As of PR #21 (later than version 1.1) WebDAV Daemon will report itself as compliance levels 1 and 2 instead of just 1. As far as I'm aware it is not compliant with class 2.
The move to report compliance without actually supporting it correctly was a pragmatic decision to get some clients to interact with the server (see #17 ).
Before the next release this must be fixed. According to RFC 4918 compliance class 2 requires the server MUST:
DAV:supportedlockproperty,DAV:lockdiscoverypropertyTime-Outresponse headerLock-Tokenrequest header.And SHOULD also support the
Timeoutrequest header