Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Sun, 30 Oct 2011 21:06:32 +0000 (UTC)
From: "Jan Lehnardt (Closed) (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <106303307.38848.1320008792264.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (COUCHDB-676) trailing slash in path cannot be
 recovered by external process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jan Lehnardt closed COUCHDB-676.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3
                   1.2
    
> trailing slash in path cannot be recovered by external process
> --------------------------------------------------------------
>
>                 Key: COUCHDB-676
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-676
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 0.11
>            Reporter: Andrew Straw
>             Fix For: 1.2, 1.3
>
>
> I modified the example given in the ExternalProcesses wiki page to return exactly the request line and queried the external process with both a trailing slash ( http://127.0.0.1:5984/test/_test/ ) and no trailing slash ( http://127.0.0.1:5984/test/_test ). The request line is exactly the same for these two cases.
> This is problematic because external processes may treat these cases differently. For example, Django's CommonMiddleware class redirects any "path" to "path/" if there is a view at "path/" but not at "path", which is usually the case for a default view of a Django app. When using Django with couchdb-wsgi, this results in an infinite redirect loop because although Django issues a redirect to "path/", couchdb-wsgi emits "path" as the path.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira