couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Bisbee (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (COUCHDB-89) DELETE on a DB returns 200 and not 202 as documented
Date Tue, 21 Feb 2012 22:48:56 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sam Bisbee closed COUCHDB-89.
-----------------------------


Resolved for a while. Closing.
                
> DELETE on a DB returns 200 and not 202 as documented
> ----------------------------------------------------
>
>                 Key: COUCHDB-89
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-89
>             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 (http://wiki.apache.org/couchdb/HttpDatabaseApi) 
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message