[
https://issues.apache.org/jira/browse/COUCHDB-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912867#action_12912867
]
Sebastian Cohnen commented on COUCHDB-891:
------------------------------------------
The problem with GET is that the length of the request is limited by (browser)
implementation - RFC 2616 [1] does not specify a limit to the URI length. I
think it's a very bad behavior if GET with keys works for X keys, but no longer
for X+1. I'm also not sure what to win by this change...
[1] RFC 2616, 3.2.1 General Syntax:
The HTTP protocol does not place any a priori limit on the length of
a URI. Servers MUST be able to handle the URI of any resource they
serve, and SHOULD be able to handle URIs of unbounded length if they
provide GET-based forms that could generate such URIs. A server
SHOULD return 414 (Request-URI Too Long) status if a URI is longer
than the server can handle (see section 10.4.15).
Note: Servers ought to be cautious about depending on URI lengths
above 255 bytes, because some older client or proxy
implementations might not properly support these lengths.
> Allow ?keys=["a","b"] for GET to _view and _list
> ------------------------------------------------
>
> Key: COUCHDB-891
> URL: https://issues.apache.org/jira/browse/COUCHDB-891
> Project: CouchDB
> Issue Type: New Feature
> Components: HTTP Interface
> Affects Versions: 1.0.1
> Environment: -
> Reporter: Michael Fellinger
> Priority: Minor
> Fix For: 1.0.2
>
>
> The idea was already described back in 2008 when the POST
> {"keys":["key1","key2"]} API was introduced.
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/200811.mbox/%[email protected]%3e
> I'm looking at the source right now, but can't figure out how to implement
> this at the moment, and I'd love this to be part of CouchDB proper.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
