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 48576] MOVE or COPY in WebDAV fails with 404 when file extension is changed
Date Mon, 02 May 2011 18:50:14 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48576

--- Comment #3 from Wim Lewis <wiml@omnigroup.com> 2011-05-02 18:50:14 UTC ---
I agree that this seems like a bug. The WebDAV WG decided not to try to figure
out the right interaction between DAV and content negotiation, so it's probably
best to just disable MultiViews on a DAV directory, but Apache's current
behavior seems unambiguously wrong.

The general case that causes this problem for me is MOVEing a collection to a
destination URL which is only mapped as a result of content-negotiation. For
example, if I have file Foo.txt and collection Bar, then moving Bar to Foo will
fail with 404.

IMHO Apache should do one of:

1: Fail with 412 if Overwrite: F was sent; succeed if Overwrite: T was sent.
2: Succeed whether or not Overwrite: T was sent (on the theory that you're not
overwriting anything)
3: Fail with another 4xx error code such as 409 Conflict.

I think #1 is probably most correct. #2 is probably closest to what most
clients want, but I don't think it is truly correct from a webdav point of
view: The Foo resource does actually exist, even though "overwriting" it does
not result in the loss of any data.

#3 would be a compromise to keep Apache's current behavior but return a more
accurate error code.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message