From: Christian Neukirchen <chneukirchen@gmail.com>
To: rack-devel@googlegroups.com
Subject: Ad. Improve multipart parsing support for UAs that don't correctly escape Content-Disposition filenames.
Date: Thu, 21 Jan 2010 13:54:43 +0100 [thread overview]
Message-ID: <e064621a1001210454j4b59eec2w63ddaf40f4819fb9@mail.gmail.com> (raw)
http://github.com/rack/rack/commit/a36ac970fd682f07c3e57756542791679f5fcf84
We spell quotes as quotes, right?
Also I think test/multipart/filename_with_unescaped_qoutes will likely
break correct behavior, but I can't show that atm.
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
next reply other threads:[~2010-01-21 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 12:54 Christian Neukirchen [this message]
2010-01-21 14:07 ` Ad. Improve multipart parsing support for UAs that don't correctly escape Content-Disposition filenames Joshua Peek
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=e064621a1001210454j4b59eec2w63ddaf40f4819fb9@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).