Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <26967540.454491282250716246.JavaMail.jira@thor>
Date: Thu, 19 Aug 2010 16:45:16 -0400 (EDT)
From: "Benoit Chesneau (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-230) Add Support for Rewritable URL
In-Reply-To: <1964398746.1233345179738.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12900448#action_12900448 ] 

Benoit Chesneau commented on COUCHDB-230:
-----------------------------------------

Following thread on ml

Imo Path alias shouln't be in vhosts but in its own section since this is not a vhost but more an "aliases" section is we follow the apache server wording. 3 questions anyway :

1) What happend anyway if a couchapp is self configuring but another app with same name already exist ?

2) What happend if path replace db path

3) security concern how to make sure a couchapp won't self configure even if the user is connected as admin ?

I think anyway for 2, that having it in /_root or /_/ would be better so api always available. Or at least, this prefix should be configurable (/ , /app or watever). 

> Add Support for Rewritable URL
> ------------------------------
>
>                 Key: COUCHDB-230
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-230
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Patrick Aljord
>             Fix For: 1.0.2
>
>
> It would be good if couchdb would allow to rewrite urls so that instead of having to write that:
> http://127.0.0.1:5984/blogdb/_design/sofa/account.html
> I could just write:
> http://127.0.0.1:5984/blogdb/account
> It could be done with the web server but having the rewritten rules in the db would make it a bit easier for replication so we don't have to write the rules on each web server where a db gets replicated.
> Here are a few propositions from davisp:
> <davisp> alisdair: how so? rewriting urls should be in _design documents, since they're in _design docs they should be limited to per db namespaces
> <davisp> bobesponja: I don't know that anyone has looked at it seriously, but my first guess is that we'd just make a _design/doc "urls" member that's a list of regex's and targets as is fairly standard practice
> <davisp> bobesponja: or perhaps, regex's -> erlang handler
> <davisp> the second might not be as fun

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.