From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Patch: Make CGI handler obey rack spec for the greater good
Date: Sun, 13 Jun 2010 18:11:47 -0300 [thread overview]
Message-ID: <6B5DF158-7394-42E7-AF34-830E016E7854@gmail.com> (raw)
In-Reply-To: <9c6dabb0-9ccc-45af-b370-c84a1527d6ad@k39g2000yqd.googlegroups.com>
On 12 Jun 2010, at 15:46, Max Cantor wrote:
> On May 20, 5:10 pm, James Tucker <jftuc...@gmail.com> wrote:
>> On 20 May 2010, at 14:36, Max Cantor wrote:
>>> Do you feel like there's a good reason to not make the CGI handler's
>>> input stream rewindable? Every time I update rack, I have to re-patch
>>> it myself, because it never works. It seems pretty unintuitive to
>>> require adding middleware just to make the CGI handler work at all.
>>
>> I just don't see really good reasons to buffer for the sake of buffering.
>
> I'm not suggesting that we buffer for the sake of buffering... the CGI
> handler literally does not work for me without this patch. I don't
> think I'm doing anything very idiosyncratic: Just a basic rack app
> with lighttpd. If there's some way I can reconfigure my environment
> to obviate the need for this patch, I can do that, but it seems like
> the handler's lack of adherence to the spec is making it break.
The spec went the way of requiring rewind. I'm not sure what the conditions are that $stdin isn't rewindable, but your patch is valid to solve the problem. Sadly, it just missed release :-/
next prev parent reply other threads:[~2010-06-13 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 13:24 Patch: Make CGI handler obey rack spec for the greater good Max Cantor
2010-05-20 14:09 ` James Tucker
2010-05-20 17:36 ` Max Cantor
2010-05-20 21:10 ` James Tucker
2010-06-12 18:46 ` Max Cantor
2010-06-13 21:11 ` James Tucker [this message]
2010-06-29 10:27 ` Hongli Lai
2010-06-29 10:44 ` James Tucker
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=6B5DF158-7394-42E7-AF34-830E016E7854@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).