From: Martin Posthumus <firstname.lastname@example.org>
To: Eric Wong <email@example.com>
Subject: Re: Support for Rack 3 headers formatted as arrays
Date: Mon, 12 Dec 2022 10:52:05 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> OK. unicorn has no choice to support all Rack as long as Rack <= 2
> applications exist...
Understood, I just wanted to show that I'm reasonably confident this
isn't due to something weird I was doing in application code, and that
ultimately I couldn't find any workaround that didn't involve
monkeypatching either Rack or Unicorn.
> Does this work for you?
Indeed it does!
> Yeah, I haven't looked deeply at Rack 3 support and hate dealing
> with the culture of breaking changes prevalent in the Ruby world :<
Yeah, I get it. To be fair the array representation probably makes more
sense for a header with multiple values, but downstream in practice it
means you have to deal with both.
next prev parent reply other threads:[~2022-12-12 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 21:52 Support for Rack 3 headers formatted as arrays Martin Posthumus
2022-12-10 2:42 ` Eric Wong
2022-12-12 15:52 ` Martin Posthumus [this message]
2022-12-25 22:56 ` Eric Wong
2022-12-27 8:17 ` Jean Boussier
2023-01-11 11:12 ` Jean Boussier
2023-01-11 11:40 ` Eric Wong
2023-01-11 11:44 ` Jean Boussier
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:
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).