couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Curt Arnold (JIRA)" <>
Subject [jira] Commented: (COUCHDB-383) HTTP get parameter strictness/looseness
Date Thu, 18 Jun 2009 19:04:07 GMT


Curt Arnold commented on COUCHDB-383:

This feature/bug relates to COUCHDB-257 which addressed the inability to work around IE's
overly aggressive caching of XmlHttpRequests.  A potential work around would be to throw in
an extra ignored parameter with a constantly changing value to prevent the inappropriate cache
hit, however this does not work since CouchDB returns a query_parse_error for the extra parameter.

I have not observed other queries accepting extra parameters either with or without an ignore_extra
parameter.  I'm using 0.10.0a777361 which is a few weeks old, so perhaps that behavior have
changed in the interim.

I vote relax.

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

View raw message