From: mateo <mateo.murphy@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Rack multipart - Content-Type implies File IO?
Date: Thu, 18 Feb 2010 08:53:11 -0800 (PST) [thread overview]
Message-ID: <1134f52d-c746-44f3-aa24-f3b5061c3a22@d3g2000vbr.googlegroups.com> (raw)
I found a post about this from may, but no resolution. The problem is
that the multipart parsing treats any part with a content-type as a
file, even if there's no filename in the Content-Disposition. This
isn't a problem with most user agents, but it is with some, and I'm
not sure it makes sense. Any thoughts?
next reply other threads:[~2010-02-18 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 16:53 mateo [this message]
2010-02-18 22:09 ` Rack multipart - Content-Type implies File IO? Mark Goris
2010-02-18 22:19 ` 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=1134f52d-c746-44f3-aa24-f3b5061c3a22@d3g2000vbr.googlegroups.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).