couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Lenz (JIRA)" <>
Subject [jira] Commented: (COUCHDB-89) DELETE on a DB returns 200 and not 202 as documented
Date Sun, 06 Jul 2008 21:43:31 GMT


Christopher Lenz commented on COUCHDB-89:

The HTTP spec says: "A successful response SHOULD be 200 (OK) if the response includes an
entity describing the status, 202 (Accepted) if the action has not yet been enacted, or 204
(No Content) if the action has been enacted but the response does not include an entity."

The deletion is immediately performed by CouchDB, so 202 is inappropriate, and as the response
contains a JSON body ({ok: true} IIRC), 204 would be incorrect, too. That leaves us with 200

So, this should indeed be updated in the Wiki, please go forward and update it!

> DELETE on a DB returns 200 and not 202 as documented
> ----------------------------------------------------
>                 Key: COUCHDB-89
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>         Environment: Ubuntu Linux x86_64, CouchDB From SVN, revision 674345
>            Reporter: Shahar Evron
> When deleting an existing database, all works ok but the returned HTTP code is 200 and
not 202 as documented ( 
> In fact, the documentation is a bit ambigous because it says '202 OK' and not '202 Accepted'
or '200 OK'. 
> While 202 makes more sense to me, this might be intentional in which case let me know
and I will update the Wiki (or you do it ;) )

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

View raw message