From: Christian Neukirchen <chneukirchen@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: RQFR: multipart bug
Date: Fri, 06 Nov 2009 19:01:48 +0100 [thread overview]
Message-ID: <m2bpjfilbn.fsf@gmail.com> (raw)
> Introduce failing test case for multipart parser when it slices
> exactly on a boundary and patch multipart parser so it passes it -
> the failing test case comes with a sample payload specific to the
> fact that the default bufsize used by the multipart parser is
> exactly 16384. should this default be changed, the test will no
> longer apply.
http://github.com/bloom/rack/commit/8f4bfced74e7a07d0f0f47705b763c7efc2f2aa7
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
next reply other threads:[~2009-11-06 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 18:01 Christian Neukirchen [this message]
2009-11-11 20:53 ` RQFR: multipart bug Bosko Milekic
2009-12-09 5:55 ` Bosko Milekic
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=m2bpjfilbn.fsf@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).