[ https://issues.apache.org/jira/browse/COUCHDB-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722505#action_12722505
]
Vinay Sajip commented on COUCHDB-383:
-------------------------------------
I don't see that this is particularly related to COUCHDB-257 - that issue is about HTTP headers,
this is about interpretation of HTTP query parameters.
> HTTP get parameter strictness/looseness
> ---------------------------------------
>
> Key: COUCHDB-383
> URL: https://issues.apache.org/jira/browse/COUCHDB-383
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 1.0
> Environment: Linux Debian 5.0 (VMware image)
> Reporter: Simon Thulbourn
> Assignee: Paul Joseph Davis
> Priority: Minor
> Fix For: 0.10
>
>
> The use of GET params in a URL is either too loose or too strict depending on your point
of view.
> Adding extra GET params that are not needed to a query works on every request except
for /dbname/_all_docs, in this event CouchDB returns an error.
> Test Case:
> /foobar/_all_docs?callback=jsonp1244562168058&_=1244562168079
> Returns: jsonp1244562168058({"error":"query_parse_error","reason":"Invalid URL parameter:
\"_\""});
> NOTE: this is not just a JSONP error, this is just how I found it.
> Ideally, CouchDB either needs to accept this or to error on every request with that contains
erroneous GET parameters.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|