Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Is mod_dav fully compliant with the WebDAV specification RFC 2518?

April 26, 2017compliant fully mod_dav rfc specification WebDAV

0

Posted

Is mod_dav fully compliant with the WebDAV specification RFC 2518?

2 Answers

0

Posted

mod_dav has a few items that cause it to be not fully compliant with RFC 2518. The cost for implementation was considered too high, and these issues are not present in typical operation. They may be fixed in some future version of mod_dav. • is not respected during a COPY or MOVE. In fact, the entire request body is ignored. Section 8.8.2 also states that live properties must be duplicated as dead properties at the target. In mod_dav’s implementation, both sources and targets necessarily have the same set of live properties. It would be incorrect to turn a target’s property from live to dead, so the RFC-required duplication does not occur. • Locks do not record the authentication principal, nor do they enforce the same principal to be authenticated to use the lock. This contradicts section 6.3. This has been mostly fixed with the 1.0 release. Some issues with POST need to be documented. • XML Namespace URIs and element names are treated as a tuple, rather than co

0

Posted

mod_dav has a few items that cause it to be not fully compliant with RFC 2518. The cost for implementation was considered too high, and these issues are not present in typical operation. They may be fixed in some future version of mod_dav. • is not respected during a COPY or MOVE. In fact, the entire request body is ignored. Section 8.8.2 also states that live properties must be duplicated as dead properties at the target. In mod_dav’s implementation, both sources and targets necessarily have the same set of live properties. It would be incorrect to turn a target’s property from live to dead, so the RFC-required duplication does not occur. • Locks do not record the authentication principal, nor do they enforce the same principal to be authenticated to use the lock. This contradicts section 6.3. This has been mostly fixed with the 1.0 release. Some issues with POST need to be documented. • XML Namespace URIs and element names are treated as a tuple, rather than co