[tahoe-lafs-trac-stream] [tahoe-lafs] #1764: tahoe webapi gives HTTP 410 Gone for files that may actually come back

[tahoe-lafs]

#1764: tahoe webapi gives HTTP 410 Gone for files that may actually come back
----------------------------------+----------------------------------------
     Reporter:  ChosenOne         |      Owner:  ChosenOne
         Type:  defect            |     Status:  new
     Priority:  normal            |  Milestone:  1.10.0
    Component:  code-frontend-    |    Version:  1.9.1
  web                             |   Keywords:  http standards test-needed
   Resolution:                    |
Launchpad Bug:                    |
----------------------------------+----------------------------------------
Changes (by davidsarah):

 * keywords:  http standards => http standards test-needed
 * owner:  davidsarah => ChosenOne


Old description:

> From RFC 2616 about HTTP 410 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''

New description:

 From RFC 2616 about HTTP 410 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''

--

Comment:

 If that patch doesn't break some tests, the test coverage was incomplete!
 :-) +1 on changing this, though.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1764#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage