couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-383) HTTP get parameter strictness/looseness
Date Mon, 15 Jun 2009 22:30:07 GMT

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

Chris Anderson commented on COUCHDB-383:
----------------------------------------

I vote relax!

> 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
>            Priority: Minor
>
> 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.


Mime
View raw message