unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Samuel Williams <samuel@oriontransfer.net>
Cc: unicorn-public@yhbt.net
Subject: Re: Is Rack partial hijack supported?
Date: Thu, 1 Sep 2022 21:53:36 +0000	[thread overview]
Message-ID: <20220901215336.M235468@dcvr> (raw)
In-Reply-To: <20220829081415.GA7335@dcvr>

Eric Wong <e@yhbt.net> wrote:
> Couldn't Rack::Chunked be made a no-op for everything aside from
> HTTP/1.1?  That would cause less problems for existing Rack <=2.x
> users wanting to upgrade.  It's already a no-op for HTTP/1.0...
> (cf. rack/chunked.rb::chunkable_version? )

I don't know if you pay attention to rack-devel, but I've posted
a proposal (patches || pull request) to undeprecate Rack::Chunked, here:

Or if you don't want to deal with Google and want to view the whole thread +
automated patch application from hunk-header links:

> Anyways I'll wait a bit for rack 3 to finalize since I'm busy
> with other stuff atm.

Any ETA on Rack 3?

      reply	other threads:[~2022-09-01 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  5:56 Is Rack partial hijack supported? Samuel Williams
2022-08-29  6:42 ` Eric Wong
2022-08-29  7:19   ` Samuel Williams
2022-08-29  8:14     ` Eric Wong
2022-09-01 21:53       ` Eric Wong [this message]

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:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220901215336.M235468@dcvr \
    --to=e@80x24.org \
    --cc=samuel@oriontransfer.net \
    --cc=unicorn-public@yhbt.net \


* 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).