couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-973) Return 410 when GETing a previously deleted document (rather than 404)
Date Thu, 13 Jan 2011 02:26:45 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981090#action_12981090
] 

Randall Leeds commented on COUCHDB-973:
---------------------------------------

Since the document may be recreated at any time the server "does not know...whether or not
the condition is permanent". Seems pretty clear cut to me.
Also, since this *is* available in the response body clients that don't care can just look
at the response code while clients that do care can inspect the body.
This sounds like a good argument to make to a client library author when asking them to expose
the response body of a 404 (if they hide the HTTP details from you generally).

> Return 410 when GETing a previously deleted document (rather than 404)
> ----------------------------------------------------------------------
>
>                 Key: COUCHDB-973
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-973
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: Benjamin Young
>            Priority: Trivial
>         Attachments: 410.patch
>
>
> When you GET a nonexistent doc you get (as you should) a 404 Not Found error. However,
if you GET a document that has previously existed you also get the 404 response. It would
be more informative (IMO) for the 410 Gone response code to be used. 410 Gone's intention
is for exactly this use case, and it could have some value to CouchDB developers who need
to know the document did exist.
> CouchDB is already half way there as in the body of the 404 response it does state that
the document did exist (at least prior to compaction), so outputing a 410 (again, prior to
compaction) would hopefully be a trivial patch. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message