Skip to content

Compliance class 2 #22

@couling

Description

@couling

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:

  • Support the LOCK method
  • The DAV:supportedlock property,
  • The DAV:lockdiscovery property
  • The Time-Out response header
  • The Lock-Token request header.

And SHOULD also support the

  • The Timeout request header
  • The 'owner' XML element.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions