From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.229.49.16 with SMTP id t16cs85214qcf; Tue, 14 Sep 2010 18:23:43 -0700 (PDT) Return-Path: Received-SPF: pass (google.com: domain of rack-devel+bncCLCeksuGExCdwMDkBBoEa9duEg@googlegroups.com designates 10.101.142.33 as permitted sender) client-ip=10.101.142.33; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rack-devel+bncCLCeksuGExCdwMDkBBoEa9duEg@googlegroups.com designates 10.101.142.33 as permitted sender) smtp.mail=rack-devel+bncCLCeksuGExCdwMDkBBoEa9duEg@googlegroups.com; dkim=pass header.i=rack-devel+bncCLCeksuGExCdwMDkBBoEa9duEg@googlegroups.com Received: from mr.google.com ([10.101.142.33]) by 10.101.142.33 with SMTP id u33mr258240ann.42.1284513823104 (num_hops = 1); Tue, 14 Sep 2010 18:23:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:x-beenthere:received:mime-version :received:received:date:in-reply-to:x-ip:references:user-agent :x-http-useragent:message-id:subject:from:to:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe:content-type :content-transfer-encoding; bh=N8nbRl3uPp7PDSk+8d1v66NaNZbPAs+P7xI0XpJeWIU=; b=OmoZHkl0n5bWVxgw0bTq4OXdPs/Cv9HajFhx9BYwUGRC0QeEtZXX+ubI+0beMSZ5QJ mmXXhvCeasyl+Vl2zx3aNOcF+jXuy1pDUHIv60vxYDOby5lHsIteVt27GNFMwCyKcvPK TZYZWz6hH13T8J2GXK7WUXdxVeRJgsdRx8Rxk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-beenthere:mime-version:date:in-reply-to:x-ip:references :user-agent:x-http-useragent:message-id:subject:from:to :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe:content-type:content-transfer-encoding; b=rx3LMS+dMR4zixjAzeh5Oyk4XhmlipcFGo6fiOUSPRIFWwnZHN34a8Bp/jTGot7b5j loKQ93YjFnfHwQcJOX7nDyvAqnvAF+Ed9lwVuRBYMFgRpSgx8+P/30Uft4EFsZUYSEpG dpeJly3LHtRNb0+b2jhl/xDuVaYHs5+ICK7WA= Received: by 10.101.142.33 with SMTP id u33mr45000ann.42.1284513821619; Tue, 14 Sep 2010 18:23:41 -0700 (PDT) X-BeenThere: rack-devel@googlegroups.com Received: by 10.100.49.22 with SMTP id w22ls229740anw.2.p; Tue, 14 Sep 2010 18:23:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.62.20 with SMTP id p20mr49853ank.18.1284513820588; Tue, 14 Sep 2010 18:23:40 -0700 (PDT) Received: by k17g2000prf.googlegroups.com with HTTP; Tue, 14 Sep 2010 18:23:40 -0700 (PDT) Date: Tue, 14 Sep 2010 18:23:40 -0700 (PDT) In-Reply-To: <7efe2e10-6029-4640-b1bb-1de6a38aeb58@a19g2000vbi.googlegroups.com> X-IP: 218.45.212.2 References: <86810130-684d-413f-aa69-a56f170459e6@m1g2000vbh.googlegroups.com> <7efe2e10-6029-4640-b1bb-1de6a38aeb58@a19g2000vbi.googlegroups.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.5 Safari/534.7,gzip(gfe) Message-ID: Subject: Re: Rack environment encoding From: naruse To: Rack Development X-Original-Sender: yui.naruse@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: Sender: rack-devel@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 9=E6=9C=8813=E6=97=A5, =E5=8D=88=E5=BE=8C11:08, Hongli Lai wrote: > So here's a new proposal: > - All required Rack variables must be ASCII, except for HTTP_ > variables. Seeing Rack Spec, required variable is REQUEST_METHOD, SCRIPT_NAME, PATH_INFO, QUERY_STRING, SERVER_NAME, and SERVER_PORT. http://rack.rubyforge.org/doc/SPEC.html They are from PEP333 and RFC3875. http://www.python.org/dev/peps/pep-0333/ http://www.ietf.org/rfc/rfc3875.txt By those specs, their content is limited in ASCII. So these encoding can be US-ASCII (or an ASCII compatible encoding). > - HTTP_ variables must be binary. Yes, so their encoding should be ASCII-8BIT. > - REQUEST_URI, if exists, must be ASCII. This is the only requirement, > I'm not proposing standardizing its meaning or requiring that it > exists. REQUEST_URI is not defined in PEP333 nor RFC3875. But RFC3050 and Apache's extension seems to be related. http://www.ietf.org/rfc/rfc3050.txt http://httpd.apache.org/docs/2.0/en/mod/mod_setenvif.html They say it is a part of URI, so it must be in ASCII. > - All other variables can have arbitrary encodings (i.e. no > standardizations). > > Outstanding issues: > - Should SERVER_NAME be ASCII or UTF-8? I'm fine with either. SERVER_NAME's content is limited within ASCII characters. So its encoding should be US-ASCII.