From: Christian Neukirchen <chneukirchen@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: [PATCH] Fix handling of multipart uploads where the filename includes a semicolon.
Date: Thu, 8 Oct 2009 13:31:44 +0200 [thread overview]
Message-ID: <e064621a0910080431h7c131273m16b2986e8428e910@mail.gmail.com> (raw)
In-Reply-To: <3543b06a-1f03-4d00-aeb3-cd65cd0ab67e@o21g2000vbl.googlegroups.com>
On Thu, Oct 8, 2009 at 9:00 AM, YoNoSoyTu <drodrigueztroitino@gmail.com> wrote:
>
> Hello,
>
> Rack 1.0.0 and the current Rack master branch includes a bug when
> parsing a multipart upload, where one of the filenames include a
> semicolon ";". Currently the filename get truncated at the semicolon.
> The fix uses the regular expression used by Ruby cgi.rb to parse
> correctly the filename parameter when it includes the semicolon. A
> test case is also included.
I think this looks good, comments? Should go to rack-1.0 as well.
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
prev parent reply other threads:[~2009-10-08 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 7:00 [PATCH] Fix handling of multipart uploads where the filename includes a semicolon YoNoSoyTu
2009-10-08 11:31 ` Christian Neukirchen [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=e064621a0910080431h7c131273m16b2986e8428e910@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).