couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Candler (JIRA)" <>
Subject [jira] Commented: (COUCHDB-383) HTTP get parameter strictness/looseness
Date Sun, 21 Jun 2009 20:34:07 GMT


Brian Candler commented on COUCHDB-383:

I'd say there are dragons in accepting random unknown query strings too. A few times I have
done something like
instead of

(or is it the other way round?) Having erroneous parameters fail silently is not, IMO, very
helpful. However I agree that the situation wasn't very consistent as it was.

Having "map=true" doesn't seem sensible to me, given that it's just the negative of "reduce=false".

Having views default to reduce=false would suit me well (i.e. if you want it reduced, you
have to ask for reduce=true), but would be hugely non backwards compatible. Ditto for your
suggestion of _map and _red.

Perhaps we could even have multiple reduce functions behind the same map - so you'd have to
select which one you wanted anyway.

> HTTP get parameter strictness/looseness
> ---------------------------------------
>                 Key: COUCHDB-383
>                 URL:
>             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.

View raw message