rubygems
/
puma
1
0
Fork 0
Code Packages Releases Activity

Add note about HTTP method change in 6.0 (#3015) 

[ci skip]
This commit is contained in:
Nate Berkopec 2022-11-11 19:38:03 +09:00 committed by GitHub
parent f323d129bc
commit d0dc3e44df
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
6.0-Upgrade.md
View File

@ -45,6 +45,7 @@ Check the following list to see if you're depending on any of these behaviors:
1. We've removed the following constants: `Puma::StateFile::FIELDS`, `Puma::CLI::KEYS_NOT_TO_PERSIST_IN_STATE` and `Puma::Launcher::KEYS_NOT_TO_PERSIST_IN_STATE`, and `Puma::ControlCLI::COMMANDS`.
1. We no longer support Ruby 2.2, 2.3, or JRuby on Java 1.7 or below.
1. The behavior of `remote_addr` has changed. When using the set_remote_address header: "header_name" functionality, if the header is not passed, REMOTE_ADDR is now set to the physical peeraddr instead of always being set to 127.0.0.1. When an error occurs preventing the physical peeraddr from being fetched, REMOTE_ADDR is now set to the unspecified source address ('0.0.0.0') instead of to '127.0.0.1'
1. Previously, Puma supported anything as an HTTP method and passed it to the app. We now only accept the 8 HTTP methods defined in RFC 9110.
Then, update your Gemfile:

2
History.md
View File

@ -11,7 +11,7 @@
* The following classes are now part of Puma's private API: `Client`, `Cluster::Worker`, `Cluster::Worker`, `HandleRequest`. ([#2988])
* Configuration constants like `DefaultRackup` removed ([#2928])
* Extracted `LogWriter` from `Events` ([#2798])
* Only accept the standard 8 HTTP methods, others rejected with 501. ([#2932])
* Features
* Increase throughput on large (100kb+) response bodies by 3-10x ([#2896], [#2892])