[COUCHDB-383] HTTP get parameter strictness/looseness

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 0.10
• Component/s: HTTP Interface

Environment

Linux Debian 5.0 (VMware image)

• Assignee: Paul Joseph Davis
• Reporter: Simon Thulbourn
• Created: 15/Jun/09 09:16
• Updated: 22/Feb/12 05:24
• Resolved: 18/Jun/09 23:44

Description

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.

Issue Links

• is related to: COUCHDB-257 HTTP caching headers make Internet Explorer experience poor