From: Christopher Meiklejohn <christopher.meiklejohn@gmail.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: Sat, 25 Feb 2012 22:07:05 -0800 (PST) [thread overview]
Message-ID: <473412.1461.1330236425377.JavaMail.geo-discussion-forums@vbtb2> (raw)
In-Reply-To: <14001171.3103.1316073882534.JavaMail.geo-discussion-forums@yqcd38>
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
Is there a bug open for this? It appears to still be a problem.
On Thursday, September 15, 2011 4:04:42 AM UTC-4, Marcelo Barbudas wrote:
>
> Actually this happens if you have for some reason in your request %%.
[-- Attachment #2: Type: text/html, Size: 348 bytes --]
prev parent reply other threads:[~2012-02-27 9:44 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 ` 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' Bo Chen
2011-09-15 7:58 ` Marcelo Barbudas
2011-09-15 8:04 ` Marcelo Barbudas
2012-02-26 6:07 ` Christopher Meiklejohn [this message]
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=473412.1461.1330236425377.JavaMail.geo-discussion-forums@vbtb2 \
--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).