couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-383) HTTP get parameter strictness/looseness
Date Sun, 21 Jun 2009 16:28:07 GMT

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

Paul Joseph Davis commented on COUCHDB-383:
-------------------------------------------

I don't find it very relaxing to accept a request that is invalid just because we think we
might know what the user wanted. This may seem trivial enough but its the first step on the
path to dragons.

However, I would support adding a new parameter that is map=true to force viewing a map that
would obviously work for either map-only or map-reduce views.

Another solution I once described was to split urls like:

/db_name/_design/foo/_view/bar

becomes

/db_name/_design/foo/_map/bar
/db_name/_design/foo/_red/bar

I support the splitting from an CouchDB internals point of view plus this exact reduce=false
messiness. Obviously, that's quite a huge break for clients though.

> 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.


Mime
View raw message