Opened at 2012-06-10T18:50:23Z
Last modified at 2013-05-30T19:25:34Z
#1764 new defect
tahoe webapi gives HTTP 401 Gone for files that may actually come back — at Initial Version
Reported by: | ChosenOne | Owned by: | davidsarah |
---|---|---|---|
Priority: | normal | Milestone: | soon |
Component: | code-frontend-web | Version: | 1.9.1 |
Keywords: | http standards test-needed | Cc: | |
Launchpad Bug: |
Description
From RFC 2616 about HTTP 401 Gone:
The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent.
This response is cacheable unless indicated otherwise
the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed.
A few things are wrong about that: If the gateway could not find enough shares due to a current lack of servers, the error is in fact temporary and links to that resource may become valid again.
tahoe should instead return a 404, i.e. http.NOT_FOUND instead of http.GONE
Content-Disposition: form-data; name="replace"
on