Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates
 209.85.212.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=RcrBVxWiSYkVUalm6JTni7fRH9JTQn/TVwV7Otxfx9e2lDB/KaHnBnsE+/iGp0Donw
         WQqlNrN01ddJ4uyQj6+6ZejpyH6E8ytmTC9ev4Tv4BAzOfzG6wmybXJjQLN8iRv68Xri
         B6nDGw5a0FVtjc7BK9R4rSJ8TdAoOPL3WZ0lE=
MIME-Version: 1.0
Sender: jchris@gmail.com
In-Reply-To: <e2111bbb0907041512x4079b77cw94a9080ccffb50be@mail.gmail.com>
References: <e282921e0905051952q314ee66crd224bcf9e6264d23@mail.gmail.com>
	 <879778450905061254s7bd5365etf82d85126471a24@mail.gmail.com>
	 <e282921e0905061315n36251e88nd95e9baf618ac136@mail.gmail.com>
	 <879778450905071033n33151a5cs439e7912c9e21fbd@mail.gmail.com>
	 <6EA12004-CCBE-47F2-BE78-4C3D6F72FD2F@jasondavies.com>
	 <21614A96-E6D2-45A3-BF7F-9D1379D84782@jasondavies.com>
	 <528EC433-F1B6-4F05-8B11-74A1FC7272F7@jasondavies.com>
	 <20090704220857.GF17906@tumbolia.org>
	 <e2111bbb0907041512x4079b77cw94a9080ccffb50be@mail.gmail.com>
Date: Sat, 4 Jul 2009 15:16:42 -0700
Message-ID: <e282921e0907041516x3efaa72h232e405e2c4c5837@mail.gmail.com>
Subject: Re: Rewriting URLs
From: Chris Anderson <jchris@apache.org>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 4, 2009 at 3:12 PM, Paul Davis<paul.joseph.davis@gmail.com> wro=
te:
> On Sat, Jul 4, 2009 at 6:08 PM, Noah Slater<nslater@apache.org> wrote:
>> Hey Jason,
>>
>> On Sat, Jul 04, 2009 at 10:34:27PM +0100, Jason Davies wrote:
>>> The basic idea is you add a "rewrites": [...] member to your design doc=
.
>>> This will allow rewriting of any URLs with the prefix mydb/
>>> _design/app/_rewrite. =A0The "rewrites" member is a list of rewrite rul=
es
>>> of the form {match: ["foo/bar/<var>"], rewrite:["_view/myview",
>>> {startkey: ["<var>"], endkey: ["<var>", {}]}]
>>
>> This is great!
>>
>> Don't let me contribute stop-energy, but I am thinking that if we're goi=
ng to do
>> this, we might want to go the full way an implement this from the root U=
RI of
>> the whole CouchDB server instead.
>>
>> Best,
>>
>> --
>> Noah Slater, http://tumbolia.org/nslater
>>
>
> We've discussed where to push the URL rewriting previously. The
> biggest argument against a DB wide rewrite scheme is that _design/
> documents could end up stomping on each other pretty easily.
>
> For reference in case other people are confused, the rewrite
> capabilities would be best used by putting a proxy in front of CouchDB
> that would rewrite all urls to the appropiate CouchDB path.
>
> Something like:
>
> Rewrite http://blog.mydomain.com/ to
> http://127.0.0.1:5984/my_blog_db/_design/sofar/_rewrite/
>

Eventually this could be implemented in CouchDB itself, with a table
to lookup app-rewrites for various subdomains or ports. I think it's
important to limit what the design doc alone can do. Putting something
like a dictionary of app -> ddoc rewrites in config seems like the
right place to modify CouchDB at such a fundamental level.

Chris


--=20
Chris Anderson
http://jchrisa.net
http://couch.io