From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.142.191.1 with SMTP id o1cs92992wff; Mon, 14 Dec 2009 03:08:31 -0800 (PST) Received: from mr.google.com ([10.229.129.139]) by 10.229.129.139 with SMTP id o11mr1142680qcs.7.1260788910811 (num_hops = 1); Mon, 14 Dec 2009 03:08:30 -0800 (PST) Received: by 10.229.129.139 with SMTP id o11mr163316qcs.7.1260788909431; Mon, 14 Dec 2009 03:08:29 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.229.44.36 with SMTP id y36ls1910025qce.3.p; Mon, 14 Dec 2009 03:08:27 -0800 (PST) Received: by 10.229.19.81 with SMTP id z17mr655489qca.19.1260788907668; Mon, 14 Dec 2009 03:08:27 -0800 (PST) Received: by 10.229.19.81 with SMTP id z17mr655487qca.19.1260788907645; Mon, 14 Dec 2009 03:08:27 -0800 (PST) Return-Path: Received: from mail-qy0-f202.google.com (mail-qy0-f202.google.com [209.85.221.202]) by gmr-mx.google.com with ESMTP id 24si1032196qyk.2.2009.12.14.03.08.26; Mon, 14 Dec 2009 03:08:26 -0800 (PST) Received-SPF: pass (google.com: domain of jftucker@gmail.com designates 209.85.221.202 as permitted sender) client-ip=209.85.221.202; Received: by qyk40 with SMTP id 40so700678qyk.22 for ; Mon, 14 Dec 2009 03:08:26 -0800 (PST) Received: by 10.224.115.22 with SMTP id g22mr508563qaq.6.1260788906487; Mon, 14 Dec 2009 03:08:26 -0800 (PST) Return-Path: Received: from ?192.168.1.54? ([199.172.234.251]) by mx.google.com with ESMTPS id 4sm11645735qwe.45.2009.12.14.03.08.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 14 Dec 2009 03:08:25 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: PATH_INFO spec (with regard to ";") From: James Tucker In-Reply-To: <200912140144.41948.ibc@aliax.net> Date: Mon, 14 Dec 2009 11:08:23 +0000 Message-Id: <3D7FFCE4-366D-4BDC-B152-B2B549A6824C@gmail.com> References: <20091210223037.GB22867@dcvr.yhbt.net> <200912110119.49974.ibc@aliax.net> <66B2EAE4-0FB8-431E-939B-98FBC4FF30C5@gmail.com> <200912140144.41948.ibc@aliax.net> To: rack-devel@googlegroups.com X-Mailer: Apple Mail (2.1077) X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jftucker@gmail.com designates 209.85.221.202 as permitted sender) smtp.mail=jftucker@gmail.com; dkim=pass (test mode) header.i=@gmail.com X-Original-Sender: jftucker@gmail.com 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/7819a650518e6ba7 Sender: rack-devel@googlegroups.com List-Unsubscribe: , List-Subscribe: , Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On 14 Dec 2009, at 00:44, I=F1aki Baz Castillo wrote: > El Domingo, 13 de Diciembre de 2009, James Tucker escribi=F3: >> "Wrong" is hard to define with archaic protocol specifications that = do not >> match "common" usage patterns >=20 > I've re-checked URI/HTTP grammar and the following URI (containing = semicolon)=20 > is valid for me (perhaps I'm wrong): >=20 > = /auid/global/mydoc.xml/~~/ruleset/rule%5b@id=3D%22sip:dom.org;p=3Dabc%22%5= d This appears to be legal according the aggregate grammars in Appendix A = of both 2396 and 3986. I don't have time to track down all of the = relevant HTTP and CGI rfcs right now, but bug me later and I'll check = those too. > So, why do you say "archaic protocol specifications that do not match = 'common'=20 > usage patterns"? Things change, indeed between 2396 and 3986 there were quite some = changes to the way segments are split in URIs, however, it does not = affect this particular issue. > I expect that HTTP is not just for web servers. No comment. > But as I said I could be wrong. Please if you (or someone) can verify = me that=20 > the semicolon is invalid according to URI/HTTP BNF grammar, then I = would=20 > accept it. According to the URI grammars in RFCs 2396 and 3986 it's fine. As I said = above, I have not checked the HTTP and CGI grammars, which may well be = different / more restrictive. >=20 > Regards. >=20 >=20 > --=20 > I=F1aki Baz Castillo