DO NOT REPLY [Bug 31156] New: - Lock on null resources does not clean on timeout

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31156>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31156

Lock on null resources does not clean on timeout

           Summary: Lock on null resources does not clean on timeout
           Product: Slide
           Version: 2.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: WebDAV Server
        AssignedTo: slide-dev@jakarta.apache.org
        ReportedBy: s.gianni@thebug.it
                CC: s.gianni@thebug.it


When a lock on a null resource is acquired, everything seems fine, but if the 
lock expires after the given timeout, the resource is still there, it's 
unlocked so an unlock method is useless, and cannot be deleted.

The RFC states that :
If the resource is unlocked, for any reason, without a PUT, MKCOL, or similar 
method having been successfully executed upon it then the resource MUST return 
to the null state. 

I belive that "for any reason" means also timeout.

P.S. This was tested on 2.1 M1, not on b1 or head.

---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org