From: "Lin Jen-Shin (godfat)" <godfat@godfat.org>
To: Eric Wong <e@80x24.org>
Cc: yahns-public@yhbt.net
Subject: Re: [RFC] proxy_pass: possibly avoid breaking some middlewares
Date: Thu, 9 Apr 2015 01:23:02 +0800 [thread overview]
Message-ID: <CAA2_N1uhjw9UEhm1dt9hx6VzB_NBLQ2MaW1SmwRipQ8Fra2KOA@mail.gmail.com> (raw)
In-Reply-To: <20150408170328.GA10903@dcvr.yhbt.net>
On Thu, Apr 9, 2015 at 1:03 AM, Eric Wong <e@80x24.org> wrote:
> "Lin Jen-Shin (godfat)" <godfat@godfat.org> wrote:
>> On Wed, Apr 8, 2015 at 5:34 AM, Eric Wong <e@80x24.org> wrote:
>> > + # this probably breaks fewer middlewares than returning whatever else...
>> > + [ 500, [], [] ]
>>
>> You probably meant [ 500, {}, [] ] here?
>
> No, arrays work fine, Rack headers just need to respond to #each
> with key + value strings.
I didn't know this, and just looked at the spec. Indeed it's only
claiming this. However some middleware bundled with Rack
would try to call [ ] method with a string, in those cases,
this would probably give a type error.
I think the spec should probably also claim that it should respond to
[ ] and taking strings as keys.
> I prefer Arrays since they use less memory per-entry, but here they're
> the same cost when empty.
That's great :P
> But I'm also likely to revert this patch since it's no longer a drop-in
> replacement and the old, synchronous ProxyPass is reinstated.
After playing a bit with hijack myself, I started to wonder if hijacking
is really a good idea, exactly the reason that it would probably break
a lot of middleware...
next prev parent reply other threads:[~2015-04-08 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 21:34 [RFC] proxy_pass: possibly avoid breaking some middlewares Eric Wong
2015-04-08 10:38 ` Lin Jen-Shin (godfat)
2015-04-08 17:03 ` Eric Wong
2015-04-08 17:23 ` Lin Jen-Shin (godfat) [this message]
2015-04-08 17:32 ` Eric Wong
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/yahns/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA2_N1uhjw9UEhm1dt9hx6VzB_NBLQ2MaW1SmwRipQ8Fra2KOA@mail.gmail.com \
--to=godfat@godfat.org \
--cc=e@80x24.org \
--cc=yahns-public@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/yahns.git/
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).