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=42896>. 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=42896 Summary: dav_method_put deletes entire file when PUT with content-range fails Product: Apache httpd-2 Version: 2.2.4 Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: mod_dav AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] If a client sends a PUT message containing a content range field and an error is experienced while receiving the data, dav_method_put function will delete the entire file. For example if a client sends a request such as: PUT /davtest/1gb.txt HTTP/1.1 content-range: bytes 1048576-2097151/* User-Agent: FPDAV client/1.0 Host: mars.tivlab.westford.ibm.com Content-Length: 1048576 Connection: Keep-Alive Authorization: Basic dXNlcjpwYXNzd29yZA== is sent by the client and a network error occurs during the receipt of the message body then the entire file is deleted before the dav_method_put returns. I believe this behavior is wrong and dav_method_put should do one of the following: 1. leave the file the way it is even with the modifications. 2. restore the file to the way it was before the modifications. At the very least dav_method_put should not delete the file if the error happened before any modifications are made to the file. I realize this way of using PUT is may not be clear in any specifications but since Apache is making an attempt I would like to explore the possibility of making it more useful until a better means up updating byte ranges of a resource comes along. I am eager to discuss a short term and to discuss any future directions Apache may take to accomplish this (such as implementing the PATCH method) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
