From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.229.54.21 with SMTP id o21cs47911qcg; Fri, 9 Sep 2011 22:29:06 -0700 (PDT) Return-Path: Received-SPF: pass (google.com: domain of rack-devel+bncCK6aobj6FhCe66vzBBoEuBziUQ@googlegroups.com designates 10.216.220.208 as permitted sender) client-ip=10.216.220.208; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rack-devel+bncCK6aobj6FhCe66vzBBoEuBziUQ@googlegroups.com designates 10.216.220.208 as permitted sender) smtp.mail=rack-devel+bncCK6aobj6FhCe66vzBBoEuBziUQ@googlegroups.com; dkim=pass header.i=rack-devel+bncCK6aobj6FhCe66vzBBoEuBziUQ@googlegroups.com Received: from mr.google.com ([10.216.220.208]) by 10.216.220.208 with SMTP id o58mr213164wep.7.1315632544652 (num_hops = 1); Fri, 09 Sep 2011 22:29:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:in-reply-to:references:date :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=pjrTXwUaM0VHm2pPsF5RUOwYTBoh2HEcsbo4pCAbJ24=; b=G8mZsdXHrti7F7qSO7+cIka6REi+73rADL7irM/i5zTkFyzUVmH6hZTOnAUby/5iPU p0by+lGrFP0dcqxHzOIVZrj7lJkXG+v5vHiabX0iAvs6VtAl47h8VLYy3p7zMGAM98Xp N7/x/MvqfDacKb8Cc4Hzeqd/P77RUc1F96NQs= Received: by 10.216.220.208 with SMTP id o58mr71709wep.7.1315632542031; Fri, 09 Sep 2011 22:29:02 -0700 (PDT) X-BeenThere: rack-devel@googlegroups.com Received: by 10.227.105.160 with SMTP id t32ls18639377wbo.2.gmail; Fri, 09 Sep 2011 22:29:00 -0700 (PDT) Received: by 10.216.186.78 with SMTP id v56mr103768wem.11.1315632540832; Fri, 09 Sep 2011 22:29:00 -0700 (PDT) Received: by 10.216.194.138 with SMTP id m10mswen; Fri, 9 Sep 2011 17:11:26 -0700 (PDT) Received: by 10.227.172.130 with SMTP id l2mr224178wbz.10.1315613486367; Fri, 09 Sep 2011 17:11:26 -0700 (PDT) Received: by 10.227.172.130 with SMTP id l2mr224177wbz.10.1315613486348; Fri, 09 Sep 2011 17:11:26 -0700 (PDT) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by gmr-mx.google.com with ESMTPS id gb10si4373453wbb.3.2011.09.09.17.11.26 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 09 Sep 2011 17:11:26 -0700 (PDT) Received-SPF: pass (google.com: domain of bochen@ooyala.com designates 74.125.82.181 as permitted sender) client-ip=74.125.82.181; Received: by wyg36 with SMTP id 36so2428902wyg.40 for ; Fri, 09 Sep 2011 17:11:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.45.78 with SMTP id o56mr33575web.30.1315613486037; Fri, 09 Sep 2011 17:11:26 -0700 (PDT) Received: by 10.216.64.195 with HTTP; Fri, 9 Sep 2011 17:11:26 -0700 (PDT) In-Reply-To: References: Date: Fri, 9 Sep 2011 17:11:26 -0700 Message-ID: Subject: Re: Bug Report: Certain characters in POST form data can cause exception in rack-1.3.2/lib/rack/backports/uri/common.rb:67:in `decode_www_form_component' From: Bo Chen To: rack-devel@googlegroups.com X-Original-Sender: bochen@ooyala.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of bochen@ooyala.com designates 74.125.82.181 as permitted sender) smtp.mail=bochen@ooyala.com Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: Sender: rack-devel@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=0016367b6de67f3c7d04ac8b22ab --0016367b6de67f3c7d04ac8b22ab Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > We recently tried upgrading to rack 1.3.2 from rack 1.2.1, and found that > it throws exceptions for some POSTs with encrypted data that we have. > I have attached the stack trace (.log) and the data from the post itself > (.har saved from chrome). > > Let me know if this is a known bug, for now, we'll stay on rack 1.2. > > Thanks in advance > > *Bo Chen* > Tech Lead, Player Team | > bochen@ooyala.com | > www.ooyala.com | blog | @ooyala > --0016367b6de67f3c7d04ac8b22ab Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,
We recently tried upgrading to rack 1.3.2 from rack 1.2.1, and found tha= t it throws exceptions for some POSTs with encrypted data that we have.
I have attached the stack trace (.log) and the data from the post itse= lf (.har saved from chrome).

Let me know if this is a known bug, for now, we'll = stay on rack 1.2.

Thanks in advance

=
Bo Chen
Tech Lead, Player Team |=A0
= bochen@ooyala.com=A0|=A0
www.ooyala.com=A0|=A0blog=A0|=A0@ooy= ala

--0016367b6de67f3c7d04ac8b22ab--