From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.142.191.1 with SMTP id o1cs119715wff; Mon, 14 Dec 2009 12:50:47 -0800 (PST) Received: from mr.google.com ([10.90.141.19]) by 10.90.141.19 with SMTP id o19mr3030000agd.8.1260823844341 (num_hops = 1); Mon, 14 Dec 2009 12:50:44 -0800 (PST) Received: by 10.90.141.19 with SMTP id o19mr420661agd.8.1260823842918; Mon, 14 Dec 2009 12:50:42 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.213.77.68 with SMTP id f4ls1893210ebk.2.p; Mon, 14 Dec 2009 12:50:41 -0800 (PST) Received: by 10.213.50.76 with SMTP id y12mr707319ebf.2.1260823840725; Mon, 14 Dec 2009 12:50:40 -0800 (PST) Received: by 10.213.50.76 with SMTP id y12mr707318ebf.2.1260823840691; Mon, 14 Dec 2009 12:50:40 -0800 (PST) Return-Path: Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by gmr-mx.google.com with ESMTP id 18si582556ewy.4.2009.12.14.12.50.40; Mon, 14 Dec 2009 12:50:40 -0800 (PST) Received-SPF: neutral (google.com: 209.85.219.209 is neither permitted nor denied by best guess record for domain of ibc@aliax.net) client-ip=209.85.219.209; Received: by mail-ew0-f209.google.com with SMTP id 1so4557817ewy.28 for ; Mon, 14 Dec 2009 12:50:40 -0800 (PST) Received: by 10.213.110.14 with SMTP id l14mr3999412ebp.82.1260823837077; Mon, 14 Dec 2009 12:50:37 -0800 (PST) Return-Path: Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 10sm8739186eyz.15.2009.12.14.12.50.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 14 Dec 2009 12:50:35 -0800 (PST) From: =?iso-8859-1?q?I=F1aki_Baz_Castillo?= To: rack-devel@googlegroups.com Subject: Re: PATH_INFO spec (with regard to ";") Date: Mon, 14 Dec 2009 21:50:31 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.28-16-generic; KDE/4.3.2; x86_64; ; ) References: <20091210223037.GB22867@dcvr.yhbt.net> <200912110119.49974.ibc@aliax.net> <20091214185158.GC12789@dcvr.yhbt.net> In-Reply-To: <20091214185158.GC12789@dcvr.yhbt.net> MIME-Version: 1.0 Message-Id: <200912142150.31421.ibc@aliax.net> X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 209.85.219.209 is neither permitted nor denied by best guess record for domain of ibc@aliax.net) smtp.mail=ibc@aliax.net X-Original-Sender: ibc@aliax.net Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: X-Thread-Url: http://groups.google.com/group/rack-devel/t/5984cfeef920f24d X-Message-Url: http://groups.google.com/group/rack-devel/msg/c521cfae29a4f9c0 Sender: rack-devel@googlegroups.com List-Unsubscribe: , List-Subscribe: , Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable El Lunes, 14 de Diciembre de 2009, Eric Wong escribi=F3: > I=F1aki Baz Castillo wrote: > > I'm coding a XCAP server using Rack. XCAP is basically XPath over HTTP = in > > which there are HTTP URI's like the following: > > > > /auid/global/mydoc.xml/~~/ruleset/rule%5b@id=3D%22sip:dom.org;p=3Dabc%= 22%5d > > > > After reading RFC for URI and HTTP I think that the ";" is valid into t= he > > above URI. I also asked in a XCAP maillist and received same conclusion. > > > > Please tell me if you consider the ";" in the above URI wrong. >=20 > Hi I=F1aki, >=20 > You're missing the point, it's not that ";" is right or wrong. It's > "right" in that it's always been _accepted_ by the Mongrel family of > HTTP parsers. That's not the issue. >=20 > The issue is just whether or not the PATH_INFO variable can contain ";" > (a path-segment parameter) in it. RFC 3875 section 4.1.5 states it > cannot: >=20 > Unlike a URI path, the PATH_INFO is not URL-encoded, and cannot > contain path-segment parameters. >=20 > However, Rack is not governed by RFC 3875 and already deviates from > it when it comes to the "PATH_INFO is not URL-encoded". Ok, thanks a lot for the clarification. =2D-=20 I=F1aki Baz Castillo