couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-2538) GET /db/doc?open_revs={} produces unsual response in CouchDB 2.0
Date Wed, 28 Jan 2015 15:18:35 GMT

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

ASF subversion and git services commented on COUCHDB-2538:
----------------------------------------------------------

Commit ec31e09e540dc4916c416247d2eb8d132b51fffd in couchdb-chttpd's branch refs/heads/setup
from [~kxepal]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=ec31e09 ]

Restore <<"unknown_error">> for HTTP 500 errors

This reverts changes made in 059229777 commit allowing chttpd to send
HTTP 500 errors in the same format as httpd does, e.g.:

  {"error": "unknown_error", "reason": "function_clause", "ref": 100500}

COUCHDB-2538


> GET /db/doc?open_revs={} produces unsual response in CouchDB 2.0
> ----------------------------------------------------------------
>
>                 Key: COUCHDB-2538
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2538
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Glynn Bird
>            Assignee: Alexander Shorin
>
> In CouchDB 1.6, if you call
> /db/doc?open_revs={}, (i.e. an invalid open_revs parameter) the following response arrives:
> {Code}
> {
> error: "unknown_error",
> reason: "function_clause"
> }
> {Code}
> but in CouchDB 2.0, we get the following response:
> {Code}
> {
> error: "function_clause",
> reason: null,
> ref: 2708187554
> }
> {Code}
> * the error message is different
> * the 'reason' field as switched to the 'error' field
> This was spotted by going through the breaking PouchDB automated tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message