On 11/7/13 4:31 PM, Geoff Field wrote: > Sorry to dredge up an old thread, but this issue is NOT really resolved > properly. (Also, I noticed a post that said that this would be treated more > seriously if it was brought up again without the "RESOLVED" tag.)
Not sure what you mean by this. The issue has been taken seriously, it's just that Apache httpd doesn't release very often. > There's a known issue with the Apache server software > (https://issues.apache.org/bugzilla/show_bug.cgi?id=55306) whereby if the > directory tree being copied has a lock anywhere in it, the DAV component will > send a 424 error. Why a copy should need to be concerned about a lock is a > mystery. The existing mod_dav module didn't properly comply with the RFC for DAV that specifies that COPY methods should enforce If: headers in the request. Someone decided to fix this, but in the process they proceed to enforce some additional restrictions (specifically that the source and the parent of the source are checked for write access). In 2.2.25 and 2.4.6 we fixed the requirement of the parent, but missed the issue with the lock on the source itself. Sadly we found the second issue shortly after the releases and now we're waiting for another release cycle to get it in your hands on a release. > The so-called "Resolution" listed in the mailing lists here was simply to > break or release the locks. It's not really a fix, just a workaround. No I'd say the resolution is to apply the patch that has been written to your httpd. > The most recent release of Apache is 2.4.6 from July, but the last activity > in the bug report is from October. Any idea when the next release is due? > The Apache release policy (http://www.apache.org/dev/release.html) doesn't > seem to tell me anything significant about that. (I do realise it's an open > source project and therefore dependant on people volunteering their time.) I don't know for sure but there was some desire to do a httpd 2.4.x release in October. For other reasons unrelated to this it hasn't happened. I see what I can do to nudge things along. Unfortunately, as a fairly new httpd committer, I'm not sure how to do the releases myself yet. > In the meantime, we will all have to continue trying to remember to unlock > files before attempting a branch, tag, or other copy. Either that, or revert > to an earlier version of Apache. My suggestion would be to apply the patch to your local httpd. I'd meant to post some copy of the patches here on the list to help with this for the various mod_dav issues that are floating around out there and had forgotten to do it. I'll be sure to make a users post with these details here shortly. But for your immediate consumption for this specific issue. The following patches will work against the respective httpd versions: https://people.apache.org/~breser/httpd/2.2.x/patches/pr55306.patch https://people.apache.org/~breser/httpd/2.4.x/patches/pr55306.patch Hope this helps you.
