Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 20625 invoked from network); 17 Jan 2011 11:57:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jan 2011 11:57:34 -0000 Received: (qmail 23231 invoked by uid 500); 17 Jan 2011 11:57:33 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 22995 invoked by uid 500); 17 Jan 2011 11:57:29 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 22981 invoked by uid 99); 17 Jan 2011 11:57:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jan 2011 11:57:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ido.ran@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-iw0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jan 2011 11:57:23 +0000 Received: by iwn37 with SMTP id 37so4932719iwn.11 for ; Mon, 17 Jan 2011 03:57:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=iMBdSL40Gh7wixGBbIs4/zreoFhkrNCGa9LeDRtBSqA=; b=W3DRzGQxqmEgXviNrJSzn7M4Y7l0bBOmtSxXQ8/ExwSQWU+fxeUsWwzfmhbWF1GP7R bK1QABKkkjzQm7p+mzQmSsQt2HFWtC4TP1OTnIvE7+Do85bfIz/9LAMv++HZTgeIGPMH xeHJLY2heMvYqm7RE3WxaXfaMvX+4337GBDTY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=BTaN9daqEVOlflUnNiDgvAoBPxfpDuR+tvR2pojMxa10NieyNIUsTqHmIwOeRS42J7 vcQtAvflK962THGBytCnuJ9PmzgnFUVeOYEVi0D1dR517SyFtZRY4ngyK+2+m9sYl5F3 vZKYlukyUPWJOTpHABaqXZ38eo/DTWFjyZgMg= Received: by 10.231.191.4 with SMTP id dk4mr4093580ibb.31.1295265259764; Mon, 17 Jan 2011 03:54:19 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.118.100 with HTTP; Mon, 17 Jan 2011 03:53:59 -0800 (PST) In-Reply-To: References: From: Ido Ran Date: Mon, 17 Jan 2011 13:53:59 +0200 Message-ID: Subject: Re: What is the semicolon means in rewrite rule To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016367d6ae2b2baa1049a097153 --0016367d6ae2b2baa1049a097153 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable So any part of the url that start with semicolon is like a "variable" that can be used in "to" and "query" parts, right? So is there a difference between "from": ":db" and "from": "" Thank you, Ido. On Sat, Jan 15, 2011 at 3:46 PM, Janez =C5=A0tupar = wrote: > There is no semicolon in the rewrite rule, > > but if you think colon in ":db" - that stands for named pattern, which ca= n > be used as a variable - you can read more about it here: > http://wiki.apache.org/couchdb/Rewriting_urls , > > http://blog.couchone.com/post/443028592/whats-new-in-apache-couchdb-0-11-= part-one-nice-urlsand > http://caolanmcmahon.com/on_designs_undocumented.html > > @Benoit - maybe you could point us towards where the rewrites are > implemented - Id gladly help out with documenting its behavior if you wou= ld > be willing to guide me where to find the information. > > Regards, > > > On Sat, Jan 15, 2011 at 12:21 PM, Ido Ran wrote: > > > rewrites config: [ { "to": "../..", "from": ":db" } ] > > > > Thanks, > > Ido. > > > --0016367d6ae2b2baa1049a097153--