[
https://issues.apache.org/jira/browse/COUCHDB-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722476#action_12722476
]
Curt Arnold commented on COUCHDB-383:
-------------------------------------
For COUCHDB-257, it would be hugely beneficial to have an always accepted
parameter that is always ignored by CouchDB.
Not quite the same issue, but CouchDB (at least a few months ago) had problems
when it was behind an authenticated proxy. The credentials were processed
properly by the proxy server but they carried through to CouchDB which would
reject the request, even though credentials weren't intended to be used by
CouchDB and the request would have worked fine without credentials. There is
the potential that CouchDB may see parameters that were included for some other
layer in the processing chain. There should be at least an option to accept
unrecognized parameters.
My possibly uninformed opinion is:
1. Add an ignore=... parameter for COUCHDB-257
2. Add a strict=true|false to control whether to reject unrecognized parameters
with a default of true (behavior prior to r786337)
3. Accept reduce=false for map-only views regardless of strict setting.
4. Accept reduce=true for map-only views when strict=false.
> 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.
