Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/73#issuecomment-140896062
Hm, it seems we have broken compatibility here. What CouchDB 1.6.1 respond
on the same request:
```
$ http POST http://127.0.0.1:5984/db/_all_docs keys:='["1",2]'
HTTP/1.1 200 OK
Cache-Control: must-revalidate
Content-Type: application/json
Date: Wed, 16 Sep 2015 21:08:23 GMT
ETag: "2EDF75VE1NJ20YC70YR128RDV"
Server: CouchDB/1.6.1 (Erlang OTP/18)
Transfer-Encoding: chunked
{
"offset": 0,
"rows": [
{
"id": "1",
"key": "1",
"value": {
"deleted": true,
"rev": "4-8bce95a01cc91f50756eb75737dd3946"
}
},
{
"error": "not_found",
"key": 2
}
],
"total_rows": 26
}
```
I think 2.0 should follow the same algorithm which is more friendly for
eventual user mistakes.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
