From: Bo Chen <bochen@ooyala.com>
To: rack-devel@googlegroups.com
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'
Date: Fri, 9 Sep 2011 17:11:26 -0700 [thread overview]
Message-ID: <CAOtxbg60cZ8V4HFyZgu2zbZE-U6pBnC4DNOsWK3OwEkDYN3Pbg@mail.gmail.com> (raw)
In-Reply-To: <CAOtxbg6uDd-d6Q59LOW-NWSfCEp5AMZ8kVbE4=3WnuQkWiLsaA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
>
> 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 <http://www.ooyala.com/blog> | @ooyala<http://www.twitter.com/ooyala>
>
[-- Attachment #2: Type: text/html, Size: 1360 bytes --]
next parent reply other threads:[~2011-09-10 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOtxbg6uDd-d6Q59LOW-NWSfCEp5AMZ8kVbE4=3WnuQkWiLsaA@mail.gmail.com>
2011-09-10 0:11 ` Bo Chen [this message]
2011-09-15 7:58 ` 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' Marcelo Barbudas
2011-09-15 8:04 ` Marcelo Barbudas
2012-02-26 6:07 ` Christopher Meiklejohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOtxbg60cZ8V4HFyZgu2zbZE-U6pBnC4DNOsWK3OwEkDYN3Pbg@mail.gmail.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).