From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.204.72.79 with SMTP id l15cs331721bkj; Mon, 3 Aug 2009 23:22:03 -0700 (PDT) Return-Path: Received-SPF: pass (google.com: domain of grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com designates 10.151.43.14 as permitted sender) client-ip=10.151.43.14; Authentication-Results: mr.google.com; spf=pass (google.com: domain of grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com designates 10.151.43.14 as permitted sender) smtp.mail=grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com; dkim=pass header.i=grbounce-ceibQwUAAAB4YPBqaDIjI2bFOCxyyh3G=chneukirchen=gmail.com@googlegroups.com Received: from mr.google.com ([10.151.43.14]) by 10.151.43.14 with SMTP id v14mr13025957ybj.16.1249366922774 (num_hops = 1); Mon, 03 Aug 2009 23:22:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=domainkey-signature:received:received:x-sender:x-apparently-to :mime-version:content-type:content-transfer-encoding:received:date :in-reply-to:x-ip:references:user-agent:x-http-useragent:message-id :subject:from:to:x-google-approved:reply-to:sender:precedence :x-google-loop:mailing-list:list-id:list-post:list-help :list-unsubscribe:x-beenthere-env:x-beenthere; bh=0ZQIeC5sQZYUN0YIouiRgyTKJoygcwNSGAqjYiHcYYI=; b=rnvUb9nPed+XAJuEUZ5RlDsyBGhJZtMsQGPP9dCMnnNDdmuaQebipPIOqbKvkk1uto doZbFPy/+hD5/eg2F13agtOKb1nC/PBhDsWv56fA1bKGcQ4QbxMePtvkV0AJjsUe6soT wBUX4CV+jDiWsAOi7Y4HFnJanVBX3LjkRTmJE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlegroups.com; s=beta; h=x-sender:x-apparently-to:mime-version:content-type :content-transfer-encoding:date:in-reply-to:x-ip:references :user-agent:x-http-useragent:message-id:subject:from:to :x-google-approved:reply-to:sender:precedence:x-google-loop :mailing-list:list-id:list-post:list-help:list-unsubscribe :x-beenthere-env:x-beenthere; b=Y6Wse/Y41r9uVkQiWbCr4VMtuVAUtWeie+TbW9kCpH/g+2Yi9/J14nwiCabFhvT9/A kWvJya1NH4+qXgAAS/ZcerCLUWxjjXco5WsuSgeXBxLuuummp40Cp1TZiOPSnOWnlMhJ IRYhDpzCVd/bwhyTb2WaboZwfe/74vEoncB/I= Received: by 10.151.43.14 with SMTP id v14mr1909729ybj.16.1249366922428; Mon, 03 Aug 2009 23:22:02 -0700 (PDT) Received: by 10.176.94.14 with SMTP id r14gr1547yqb.0; Mon, 03 Aug 2009 23:21:49 -0700 (PDT) X-Sender: jimmy@deefa.com X-Apparently-To: rack-devel@googlegroups.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Received: by 10.100.249.10 with SMTP id w10mr1886218anh.17.1249359353711; Mon, 03 Aug 2009 21:15:53 -0700 (PDT) Date: Mon, 3 Aug 2009 21:15:53 -0700 (PDT) In-Reply-To: X-IP: 203.217.31.136 References: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1) Gecko/20090704 Iceweasel/3.5 (Debian-3.5-0),gzip(gfe),gzip(gfe) Message-ID: <0e727ddb-9dde-4024-b7e2-42eb03bac6b2@x5g2000prf.googlegroups.com> Subject: Re: Rack 1.0.1 maintenance release From: James To: Rack Development X-Google-Approved: scytrin@gmail.com via web at 2009-08-04 06:21:49 Reply-To: rack-devel@googlegroups.com Sender: rack-devel@googlegroups.com Precedence: bulk X-Google-Loop: groups Mailing-List: list rack-devel@googlegroups.com; contact rack-devel+owner@googlegroups.com List-Id: List-Post: List-Help: List-Unsubscribe: , X-BeenThere-Env: rack-devel@googlegroups.com X-BeenThere: rack-devel@googlegroups.com On Aug 4, 3:36=A0am, Joshua Peek wrote: > I went though most of the Lighthouse tickets and only found one that > really concerned 1.0. > > "Rack::Utils.unescape problems in Ruby 1.9.1" > =A0http://rack.lighthouseapp.com/projects/22435/tickets/48-rackutilsunes.= .. To correctly solve this issue Rack needs to make some decisions about how to mark the encoding of incoming data. Jeremy Kemper and I started a discussion on that ticket that really needs to be promoted to a mailing list. Ignoring the issue of discerning the encoding of the request query string, there's still the request body on POST requests. According to RFC2616, Rack can use the charset segment of the requests Content-Type header to determine the request body encoding and assume ISO-8859-1 if a charset isn't provided. However FF 3.5 doesn't appear to specify the charset of its UTF-8 encoded requests, which means Rack *should* (incorrectly) mark the incoming data as ISO-8859-1. Can anyone shed some light on what the correct behaviour for Rack should be? James