tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16323] New: - Cadaver/RFC 2518 locking incompatibility
Date Wed, 22 Jan 2003 12:40:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16323>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16323

Cadaver/RFC 2518 locking incompatibility

           Summary: Cadaver/RFC 2518 locking incompatibility
           Product: Tomcat 4
           Version: 4.1.18
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Servlets:WebDAV
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: pprooi@xs4all.nl


When locking files with the cadaver command line tool, it complains about "No
Lock-Token header given". It wants to see a Lock-Token header with the same
value as the lock token in the xml body.
The RFC 2518 states in 8.10.1:  "a Lock-Token response header MUST be included
in the response for every successful LOCK request for a new lock.", but the
servlet code never does this, although it does read the lock header tokens.

I've included a patch (against the 4.1.18 webdav servlet code) which adds the
token header, could you tell me if it is correct ?

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message