httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38148] - One Failed Request Can Possibly Overwrite Another Active Request's PUT
Date Fri, 06 Jan 2006 09:28:50 GMT
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=38148>.
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=38148





------- Additional Comments From jorton@redhat.com  2006-01-06 10:28 -------
I do agree that the delete-on-failed-PUT behaviour is a bug, at least in the
case of modifying an existing file.  Perhaps it is useful for the case where the
resource did not exist before.

To completely avoid concurrency problems like this mod_dav_fs would also have to
lock the file.  That should be relatively simple to do but needs further analysis.

w.r.t. doing a the stat()-after-PUT; that would not eliminate the race; another
process could still modify the file after the stat() and the returned status
code would be "wrong" again

-- 
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: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message