Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9F0AF10BD5 for ; Wed, 28 May 2014 10:58:02 +0000 (UTC) Received: (qmail 32329 invoked by uid 500); 28 May 2014 10:58:02 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 32258 invoked by uid 500); 28 May 2014 10:58:02 -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 32249 invoked by uid 99); 28 May 2014 10:58:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 10:58:02 +0000 Date: Wed, 28 May 2014 10:58:02 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (COUCHDB-2249) Fauxton generates incorrect parameters when complex keys are specified MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011011#comment-14011011 ] ASF GitHub Bot commented on COUCHDB-2249: ----------------------------------------- Github user willholley closed the pull request at: https://github.com/apache/couchdb/pull/237 > Fauxton generates incorrect parameters when complex keys are specified > ---------------------------------------------------------------------- > > Key: COUCHDB-2249 > URL: https://issues.apache.org/jira/browse/COUCHDB-2249 > Project: CouchDB > Issue Type: Bug > Security Level: public(Regular issues) > Components: Fauxton > Reporter: Will Holley > > Fauxton is not stringifying user-defined query parameters correctly (added in the "Query Options" panel). This results in a query parameter being generated for each component of the complex key. > For example, specifying a startkey of {noformat}["a","b"]{noformat} generates the URL > {noformat} > ?startkey[]=a&startkey[]=b > {noformat} > instead of: > {noformat} > ?startkey=["a","b"] > {noformat} -- This message was sent by Atlassian JIRA (v6.2#6252)