couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Chesneau (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-230) Add Support for Rewritable URL
Date Wed, 18 Aug 2010 08:11:17 GMT

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

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

actually you could already do :

example.com/foobar = /foo/_design/bar/_rewrite
*.website.com/foobar = /foo/_design/bar/_rewrite
localhost:5984/bazbam = /whatever 

and :

$vhost.example.com = /$vhost

even

$app.$vhost.example.com /$vhost/_design/$app/_rewrite

for the path based reouting we could likely introduce that too, but it need some code rewrite
to share code with rewriter. 

For local usage though I was thinking that not allowing /pathname but only /_root/pathname
would have been better to not be in conflict with the current API.

[

> 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.


Mime
View raw message