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

Paul Joseph Davis commented on COUCHDB-973:
-------------------------------------------

I almost went to say +1 but after reading the description of 410 again, I 
noticed this blurb:

> If the server does not know, or has no facility to determine, whether
> or not the condition is permanent, the status code 404 (Not Found)
> SHOULD be used instead."

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11

I don't think its super clear cut for either one. As mentioned the 
{"not_found": "deleted"} can be used to check the same condition so its not 
that we're missing any capability other than which layer we may want to deal 
with this particular case.

If I were to make a snap decision I think I would vote in favor of keeping 404 
but I'm not adverse to hearing arguments in favor of 410.


> 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.

Reply via email to