From: Jeremy Kemper <jeremy@bitsweat.net>
To: rack-devel@googlegroups.com
Subject: Consider reverting multipart parsing change
Date: Sun, 4 Jul 2010 15:20:12 -0700 [thread overview]
Message-ID: <AANLkTim8CfLLS77zg8Z8Y2NsoH6_pD5FB2YxdL38lffG@mail.gmail.com> (raw)
I think acffe8ef5 should be reverted.
To support an edge casey user-agent it removed the metadata from all
MIME parts with a Content-Type but no filename.
The idea was to have text/plain parts parse as regular params instead
of file uploads. That's reasonable, but it should be limited to
text/plain parts.
The original issue: http://rack.lighthouseapp.com/projects/22435-rack/tickets/79
jeremy
next reply other threads:[~2010-07-04 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 22:20 Jeremy Kemper [this message]
2010-07-05 22:57 ` Consider reverting multipart parsing change Mark Goris
2010-07-06 7:54 ` Jeremy Kemper
2010-07-08 5:03 ` Joshua Ballanco
2010-07-10 2:26 ` Mateo Murphy
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=AANLkTim8CfLLS77zg8Z8Y2NsoH6_pD5FB2YxdL38lffG@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).