From dev-return-4673-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Mon Jun 22 08:14:21 2009 Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 53134 invoked from network); 22 Jun 2009 08:14:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Jun 2009 08:14:20 -0000 Received: (qmail 77704 invoked by uid 500); 22 Jun 2009 08:14:30 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 77593 invoked by uid 500); 22 Jun 2009 08:14:30 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 77576 invoked by uid 99); 22 Jun 2009 08:14:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 08:14:30 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 08:14:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5B13C234C004 for ; Mon, 22 Jun 2009 01:14:07 -0700 (PDT) Message-ID: <553116745.1245658447358.JavaMail.jira@brutus> Date: Mon, 22 Jun 2009 01:14:07 -0700 (PDT) From: "Vinay Sajip (JIRA)" To: dev@couchdb.apache.org Subject: [jira] Commented: (COUCHDB-383) HTTP get parameter strictness/looseness In-Reply-To: <2022452910.1245057427347.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/COUCHDB-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722505#action_12722505 ] Vinay Sajip commented on COUCHDB-383: ------------------------------------- I don't see that this is particularly related to COUCHDB-257 - that issue is about HTTP headers, this is about interpretation of HTTP query parameters. > 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.