From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.142.191.1 with SMTP id o1cs115079wff; Mon, 14 Dec 2009 10:52:04 -0800 (PST) Received: from mr.google.com ([10.91.121.9]) by 10.91.121.9 with SMTP id y9mr638918agm.30.1260816723812 (num_hops = 1); Mon, 14 Dec 2009 10:52:03 -0800 (PST) Received: by 10.91.121.9 with SMTP id y9mr85429agm.30.1260816722415; Mon, 14 Dec 2009 10:52:02 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.204.16.73 with SMTP id n9ls1164433bka.3.p; Mon, 14 Dec 2009 10:52:00 -0800 (PST) Received: by 10.204.21.20 with SMTP id h20mr142287bkb.2.1260816720296; Mon, 14 Dec 2009 10:52:00 -0800 (PST) Received: by 10.204.21.20 with SMTP id h20mr142286bkb.2.1260816720279; Mon, 14 Dec 2009 10:52:00 -0800 (PST) Return-Path: Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by gmr-mx.google.com with ESMTP id 17si312777bwz.8.2009.12.14.10.51.59; Mon, 14 Dec 2009 10:51:59 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of normalperson@yhbt.net designates 64.71.152.64 as permitted sender) client-ip=64.71.152.64; Received: from localhost (dcvr.yhbt.net [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPSA id D1D2D1F4FA; Mon, 14 Dec 2009 18:51:58 +0000 (UTC) Date: Mon, 14 Dec 2009 18:51:58 +0000 From: Eric Wong To: rack-devel@googlegroups.com Subject: Re: PATH_INFO spec (with regard to ";") Message-ID: <20091214185158.GC12789@dcvr.yhbt.net> References: <20091210223037.GB22867@dcvr.yhbt.net> <6C9FF58B-36A8-429F-85E1-3C34CF984DF9@gmail.com> <200912110119.49974.ibc@aliax.net> MIME-Version: 1.0 In-Reply-To: <200912110119.49974.ibc@aliax.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of normalperson@yhbt.net designates 64.71.152.64 as permitted sender) smtp.mail=normalperson@yhbt.net X-Original-Sender: normalperson@yhbt.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/1e6f1469345d5922 Sender: rack-devel@googlegroups.com List-Unsubscribe: , List-Subscribe: , Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Iņaki 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=%22sip:dom.org;p=abc%22%5d > > After reading RFC for URI and HTTP I think that the ";" is valid into the > 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. Hi Iņaki, 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. 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: Unlike a URI path, the PATH_INFO is not URL-encoded, and cannot contain path-segment parameters. However, Rack is not governed by RFC 3875 and already deviates from it when it comes to the "PATH_INFO is not URL-encoded". -- Eric Wong