From: beam <rudra@rsl.ru>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Question about parse_multipart()
Date: Fri, 20 Nov 2009 00:06:05 -0800 (PST) [thread overview]
Message-ID: <88c30444-4495-4a0c-9800-d6fd974f498a@f16g2000yqm.googlegroups.com> (raw)
About commit http://github.com/rack/rack/commit/6674f3652ed19136802a0b84f1923f0b78052442
I read RFC? but not understand why we add this lines in lib/rack/
utils.rb:
330+ if content_type || filename
372+ elsif !filename && content_type
373+ body.rewind
374+
375+ # Generic multipart cases, not coming from a form
376+ data = {:type => content_type,
377+ :name => name, :tempfile => body, :head =>
head}
next reply other threads:[~2009-11-20 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 8:06 beam [this message]
2009-11-20 8:27 ` Question about parse_multipart() beam
2009-11-21 0:14 ` Mark Goris
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=88c30444-4495-4a0c-9800-d6fd974f498a@f16g2000yqm.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).