Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Mon, 8 Aug 2011 16:44:27 +0000 (UTC)
From: "max ogden (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <453755648.16951.1312821867250.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <6408726.325121294868933474.JavaMail.jira@thor>
Subject: [jira] [Updated] (COUCHDB-1026) Database names are not encoded in
 the rewriter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COUCHDB-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

max ogden updated COUCHDB-1026:
-------------------------------

    Attachment: rewrite_db_with_forward_slashes.js

Here is a futon test that exacerbates the issue. Included are two tests, one without a forward slash that passes and then a copy of that test changed to use a database containing a forward slash. The second test should fail

> Database names are not encoded in the rewriter
> ----------------------------------------------
>
>                 Key: COUCHDB-1026
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1026
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.0.1
>            Reporter: Benjamin Young
>         Attachments: encode_db_name_in_rewriter.patch, rewrite_db_with_forward_slashes.js
>
>
> If a database includes special characters (such as / "forward slash"), then the rewriter will fail to find the correct database and send a 404 error:
> {"error":"not_found","reason":"no_db_file"}
> The attached patch simply adds a url_encode step around DbName.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira