[
https://issues.apache.org/jira/browse/COUCHDB-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271175#comment-14271175
]
ASF GitHub Bot commented on COUCHDB-2538:
-----------------------------------------
GitHub user kxepal opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/17
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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kxepal/couchdb-chttpd
2538-revert-500-error-reason-changes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/17.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17
----
commit f42ae9e8050507725cb1b67bc5dcc99b03e06a5e
Author: Alexander Shorin <[email protected]>
Date: 2015-01-09T15:32:28Z
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
>
> 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)
