From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.142.191.1 with SMTP id o1cs72290wff; Sun, 13 Dec 2009 16:44:53 -0800 (PST) Received: from mr.google.com ([10.90.7.11]) by 10.90.7.11 with SMTP id 11mr6912686agg.14.1260751492980 (num_hops = 1); Sun, 13 Dec 2009 16:44:52 -0800 (PST) Received: by 10.90.7.11 with SMTP id 11mr987903agg.14.1260751488492; Sun, 13 Dec 2009 16:44:48 -0800 (PST) X-BeenThere: rack-devel@googlegroups.com Received: by 10.213.104.96 with SMTP id n32ls1481729ebo.1.p; Sun, 13 Dec 2009 16:44:46 -0800 (PST) Received: by 10.213.23.215 with SMTP id s23mr613423ebb.12.1260751486824; Sun, 13 Dec 2009 16:44:46 -0800 (PST) Received: by 10.213.23.215 with SMTP id s23mr613422ebb.12.1260751486808; Sun, 13 Dec 2009 16:44:46 -0800 (PST) Return-Path: Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by gmr-mx.google.com with ESMTP id 12si462652ewy.10.2009.12.13.16.44.46; Sun, 13 Dec 2009 16:44:46 -0800 (PST) Received-SPF: neutral (google.com: 74.125.78.24 is neither permitted nor denied by best guess record for domain of ibc@aliax.net) client-ip=74.125.78.24; Received: by ey-out-2122.google.com with SMTP id 22so647137eye.7 for ; Sun, 13 Dec 2009 16:44:46 -0800 (PST) Received: by 10.213.109.86 with SMTP id i22mr2754164ebp.58.1260751486596; Sun, 13 Dec 2009 16:44:46 -0800 (PST) Return-Path: Received: from ibc-laptop.localnet ([212.230.46.89]) by mx.google.com with ESMTPS id 15sm2725940ewy.4.2009.12.13.16.44.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 13 Dec 2009 16:44:44 -0800 (PST) From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= To: rack-devel@googlegroups.com Subject: Re: PATH_INFO spec (with regard to ";") Date: Mon, 14 Dec 2009 01:44:41 +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> <66B2EAE4-0FB8-431E-939B-98FBC4FF30C5@gmail.com> In-Reply-To: <66B2EAE4-0FB8-431E-939B-98FBC4FF30C5@gmail.com> MIME-Version: 1.0 Message-Id: <200912140144.41948.ibc@aliax.net> X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 74.125.78.24 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/3d441001aaa2cbcc Sender: rack-devel@googlegroups.com List-Unsubscribe: , List-Subscribe: , Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable El Domingo, 13 de Diciembre de 2009, James Tucker escribi=C3=B3: > "Wrong" is hard to define with archaic protocol specifications that do not > match "common" usage patterns I've re-checked URI/HTTP grammar and the following URI (containing semicolo= n)=20 is valid for me (perhaps I'm wrong): /auid/global/mydoc.xml/~~/ruleset/rule%5b@id=3D%22sip:dom.org;p=3Dabc%22%= 5d So, why do you say "archaic protocol specifications that do not match 'comm= on'=20 usage patterns"? I expect that HTTP is not just for web servers. But as I said I could be wrong. Please if you (or someone) can verify me th= at=20 the semicolon is invalid according to URI/HTTP BNF grammar, then I would=20 accept it. Regards. =2D-=20 I=C3=B1aki Baz Castillo