From: Eric Wong <e@80x24.org>
To: rack-devel@googlegroups.com
Subject: [PATCH|PULL 0/2] chunked: limit to HTTP/1.1, undeprecate
Date: Thu, 1 Sep 2022 21:45:34 +0000 [thread overview]
Message-ID: <20220901214536.5469-1-e@80x24.org> (raw)
Lets reduce the pain on end users upgrading to Rack 3.
HTTP/1.0 and HTTP/1.1 aren't going away, and I was dealing
with HTTP/0.9 until 2017.
Fwiw, probably 95% of people and organizations I know have
given up on Ruby due to constant treadmill of upgrades and
incompatibilities, so avoid giving them more reason to give
up Ruby due to more incompatibilities.
The following changes since commit 6aad5390403ca48a0ba76e426a21274385895731:
The stream argument must implement `#<<`. (#1959) (2022-08-31 14:31:46 +1200)
are available in the Git repository at:
https://80x24.org/rack.git chunk
for you to fetch changes up to e3945c3acc5a6e8d3af4cc8639dcb12fb85a8aee:
chunked: remove deprecation warning (2022-09-01 21:34:23 +0000)
----------------------------------------------------------------
Eric Wong (2):
chunked: limit to HTTP/1.1
chunked: remove deprecation warning
lib/rack/chunked.rb | 13 ++-----------
1 file changed, 2 insertions(+), 11 deletions(-)
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rack-devel/20220901214536.5469-1-e%4080x24.org.
next reply other threads:[~2022-09-01 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 21:45 Eric Wong [this message]
2022-09-01 21:45 ` [PATCH 1/2] chunked: limit to HTTP/1.1 Eric Wong
2022-09-01 21:45 ` [PATCH 2/2] chunked: remove deprecation warning 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-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=20220901214536.5469-1-e@80x24.org \
--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).