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=11658>. 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=11658 Locking a non-null resource Summary: Locking a non-null resource Product: Slide Version: 1.0.16 Stable Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: WebDAV client AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] When a non-existing resource is locked, server response is 201 with a lockDiscovery property in XML response body. WebDAV client always expects a 200 or 207 response and does not handle 201. If we modify parseResponse() method of LockMethod class as follows everything works fine: ============================== public void parseResponse(InputStream input) throws IOException, HttpException { if (status == HttpStatus.SC_OK || - status == HttpStatus.SC_MULTI_STATUS ) { + status == HttpStatus.SC_MULTI_STATUS || + status == HttpStatus.SC_CREATED ) { parseXMLResponse(input); - if ( (status == HttpStatus.SC_OK) && + if ( (status != HttpStatus.SC_MULTI_STATUS) && - (this.state instanceof WebdavState)) { String prefix = DOMUtils.findDavPrefix( =================================== I have tested this patch with IIS. Thanks -ravi -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
