actionpack 5.2.6 → 6.1.4.4

data/CHANGELOG.md

@@ -1,550 +1,542 @@
-## Rails 5.2.6 (May 05, 2021) ##
+## Rails 6.1.4.4 (December 15, 2021) ##
 
-*   Accept base64_urlsafe CSRF tokens to make forward compatible.
+*   Fix issue with host protection not allowing host with port in development.
 
-    Base64 strict-encoded CSRF tokens are not inherently websafe, which makes
-    them difficult to deal with. For example, the common practice of sending
-    the CSRF token to a browser in a client-readable cookie does not work properly
-    out of the box: the value has to be url-encoded and decoded to survive transport.
-
-    In this version, we generate Base64 urlsafe-encoded CSRF tokens, which are inherently
-    safe to transport. Validation accepts both urlsafe tokens, and strict-encoded
-    tokens for backwards compatibility.
-
-    How the tokes are encoded is controllr by the `action_controller.urlsafe_csrf_tokens`
-    config.
 
-    In Rails 5.2.5, the CSRF token format was accidentally changed to urlsafe-encoded.
+## Rails 6.1.4.3 (December 14, 2021) ##
 
-    **Atention**: If you already upgraded your application to 5.2.5, set the config
-    `urlsafe_csrf_tokens` to `true`, otherwise your form submission will start to fail
-    during the deploy of this new version.
+*    Fix issue with host protection not allowing localhost in development.
 
-    ```ruby
-    Rails.application.config.action_controller.urlsafe_csrf_tokens = true
-    ```
-
-    If you are upgrading from 5.2.4.x, you don't need to change this configuration.
 
-    *Scott Blum*, *Étienne Barrié*
+## Rails 6.1.4.2 (December 14, 2021) ##
 
+*   Fix X_FORWARDED_HOST protection.  [CVE-2021-44528]
 
-## Rails 5.2.5 (March 26, 2021) ##
-
-*   No changes.
+## Rails 6.1.4.1 (August 19, 2021) ##
 
+*   [CVE-2021-22942] Fix possible open redirect in Host Authorization middleware.
 
-## Rails 5.2.4.6 (May 05, 2021) ##
+    Specially crafted "X-Forwarded-Host" headers in combination with certain
+    "allowed host" formats can cause the Host Authorization middleware in Action
+    Pack to redirect users to a malicious website.
 
-*   Prevent regex DoS in HTTP token authentication
-    CVE-2021-22904
+## Rails 6.1.4 (June 24, 2021) ##
 
-*   Prevent string polymorphic route arguments.
+*   Ignore file fixtures on `db:fixtures:load`
 
-    `url_for` supports building polymorphic URLs via an array
-    of arguments (usually symbols and records). If a developer passes a
-    user input array, strings can result in unwanted route helper calls.
+    *Kevin Sjöberg*
 
-    CVE-2021-22885
+*   Fix ActionController::Live controller test deadlocks by removing the body buffer size limit for tests.
 
-    *Gannon McGibbon*
+    *Dylan Thacker-Smith*
 
-## Rails 5.2.4.5 (February 10, 2021) ##
+*   Correctly place optional path parameter booleans.
 
-*   No changes.
+    Previously, if you specify a url parameter that is part of the path as false it would include that part
+    of the path as parameter for example:
 
+    ```
+    get "(/optional/:optional_id)/things" => "foo#foo", as: :things
+    things_path(optional_id: false) # => /things?optional_id=false
+    ```
 
-## Rails 5.2.4.4 (September 09, 2020) ##
+    After this change, true and false will be treated the same when used as optional path parameters. Meaning now:
 
-*   No changes.
+    ```
+    get '(this/:my_bool)/that' as: :that
 
+    that_path(my_bool: true) # => `/this/true/that`
+    that_path(my_bool: false) # => `/this/false/that`
+    ```
 
-## Rails 5.2.4.3 (May 18, 2020) ##
+    *Adam Hess*
 
-*   [CVE-2020-8166] HMAC raw CSRF token before masking it, so it cannot be used to reconstruct a per-form token
+*   Add support for 'private, no-store' Cache-Control headers.
 
-*   [CVE-2020-8164] Return self when calling #each, #each_pair, and #each_value instead of the raw @parameters hash
+    Previously, 'no-store' was exclusive; no other directives could be specified.
 
+    *Alex Smith*
 
-## Rails 5.2.4.2 (March 19, 2020) ##
 
-*   No changes.
+## Rails 6.1.3.2 (May 05, 2021) ##
 
+*   Prevent open redirects by correctly escaping the host allow list
+    CVE-2021-22903
 
-## Rails 5.2.4.1 (December 18, 2019) ##
+*   Prevent catastrophic backtracking during mime parsing
+    CVE-2021-22902
 
-*   Fix possible information leak / session hijacking vulnerability.
+*   Prevent regex DoS in HTTP token authentication
+    CVE-2021-22904
 
-    The `ActionDispatch::Session::MemcacheStore` is still vulnerable given it requires the
-    gem dalli to be updated as well.
+*   Prevent string polymorphic route arguments.
 
-    _Breaking changes:_
-    *   `session.id` now returns an instance of `Rack::Session::SessionId` and not a String (use `session.id.public_id` to restore the old behaviour, see #38063)
-    *   Accessing the session id using `session[:session_id]`/`session['session_id']` no longer works with
-        ruby 2.2 (see https://github.com/rails/rails/commit/2a52a38cb51b65d71cf91fc960777213cf96f962#commitcomment-37929811)
+    `url_for` supports building polymorphic URLs via an array
+    of arguments (usually symbols and records). If a developer passes a
+    user input array, strings can result in unwanted route helper calls.
 
-    CVE-2019-16782.
+    CVE-2021-22885
 
+    *Gannon McGibbon*
 
-## Rails 5.2.4 (November 27, 2019) ##
+## Rails 6.1.3.1 (March 26, 2021) ##
 
 *   No changes.
 
 
-## Rails 5.2.3 (March 27, 2019) ##
+## Rails 6.1.3 (February 17, 2021) ##
 
-*   Allow using `public` and `no-cache` together in the the Cache Control header.
+*   Re-define routes when not set correctly via inheritance.
 
-    Before this change, even if `public` was specified in the Cache Control header,
-    it was excluded when `no-cache` was included. This change preserves the
-    `public` value as is.
+    *John Hawthorn*
 
-    Fixes #34780.
 
-    *Yuji Yaginuma*
-
-*   Allow `nil` params for `ActionController::TestCase`.
+## Rails 6.1.2.1 (February 10, 2021) ##
 
-    *Ryo Nakamura*
+*   Prevent open redirect when allowed host starts with a dot
 
+    [CVE-2021-22881]
 
-## Rails 5.2.2.1 (March 11, 2019) ##
+    Thanks to @tktech (https://hackerone.com/tktech) for reporting this
+    issue and the patch!
 
-*   No changes.
+    *Aaron Patterson*
 
 
-## Rails 5.2.2 (December 04, 2018) ##
+## Rails 6.1.2 (February 09, 2021) ##
 
-*   Reset Capybara sessions if failed system test screenshot raising an exception.
+*   Fix error in `ActionController::LogSubscriber` that would happen when throwing inside a controller action.
 
-    Reset Capybara sessions if `take_failed_screenshot` raise exception
-    in system test `after_teardown`.
+    *Janko Marohnić*
 
-    *Maxim Perepelitsa*
+*   Fix `fixture_file_upload` deprecation when `file_fixture_path` is a relative path.
 
-*   Use request object for context if there's no controller
+    *Eugene Kenny*
 
-    There is no controller instance when using a redirect route or a
-    mounted rack application so pass the request object as the context
-    when resolving dynamic CSP sources in this scenario.
 
-    Fixes #34200.
+## Rails 6.1.1 (January 07, 2021) ##
 
-    *Andrew White*
+*   Fix nil translation key lookup in controllers/
 
-*   Apply mapping to symbols returned from dynamic CSP sources
+    *Jan Klimo*
 
-    Previously if a dynamic source returned a symbol such as :self it
-    would be converted to a string implicity, e.g:
+*   Quietly handle unknown HTTP methods in Action Dispatch SSL middleware.
 
-        policy.default_src -> { :self }
+    *Alex Robbin*
 
-    would generate the header:
+*   Change the request method to a `GET` when passing failed requests down to `config.exceptions_app`.
 
-        Content-Security-Policy: default-src self
+    *Alex Robbin*
 
-    and now it generates:
 
-        Content-Security-Policy: default-src 'self'
+## Rails 6.1.0 (December 09, 2020) ##
 
-    *Andrew White*
+*   Support for the HTTP header `Feature-Policy` has been revised to reflect
+    its [rename](https://github.com/w3c/webappsec-permissions-policy/pull/379) to [`Permissions-Policy`](https://w3c.github.io/webappsec-permissions-policy/#permissions-policy-http-header-field).
 
-*   Fix `rails routes -c` for controller name consists of multiple word.
+    ```ruby
+    Rails.application.config.permissions_policy do |p|
+      p.camera     :none
+      p.gyroscope  :none
+      p.microphone :none
+      p.usb        :none
+      p.fullscreen :self
+      p.payment    :self, "https://secure-example.com"
+    end
+    ```
 
-    *Yoshiyuki Kinjo*
+    *Julien Grillot*
 
-*   Call the `#redirect_to` block in controller context.
+*   Allow `ActionDispatch::HostAuthorization` to exclude specific requests.
 
-    *Steven Peckins*
+    Host Authorization checks can be skipped for specific requests. This allows for health check requests to be permitted for requests with missing or non-matching host headers.
 
+    *Chris Bisnett*
 
-## Rails 5.2.1.1 (November 27, 2018) ##
+*   Add `config.action_dispatch.request_id_header` to allow changing the name of
+    the unique X-Request-Id header
 
-*   No changes.
+    *Arlston Fernandes*
 
+*   Deprecate `config.action_dispatch.return_only_media_type_on_content_type`.
 
-## Rails 5.2.1 (August 07, 2018) ##
+    *Rafael Mendonça França*
 
-*   Prevent `?null=` being passed on JSON encoded test requests.
+*   Change `ActionDispatch::Response#content_type` to return the full Content-Type header.
 
-    `RequestEncoder#encode_params` won't attempt to parse params if
-    there are none.
+    *Rafael Mendonça França*
 
-    So call like this will no longer append a `?null=` query param.
+*   Remove deprecated `ActionDispatch::Http::ParameterFilter`.
 
-        get foos_url, as: :json
+    *Rafael Mendonça França*
 
-    *Alireza Bashiri*
+*   Added support for exclusive no-store Cache-Control header.
 
-*   Ensure `ActionController::Parameters#transform_values` and
-    `ActionController::Parameters#transform_values!` converts hashes into
-    parameters.
+    If `no-store` is set on Cache-Control header it is exclusive (all other cache directives are dropped).
 
-    *Kevin Sjöberg*
+    *Chris Kruger*
 
-*   Fix strong parameters `permit!` with nested arrays.
+*   Catch invalid UTF-8 parameters for POST requests and respond with BadRequest.
 
-    Given:
-    ```
-    params = ActionController::Parameters.new(nested_arrays: [[{ x: 2, y: 3 }, { x: 21, y: 42 }]])
-    params.permit!
-    ```
+    Additionally, perform `#set_binary_encoding` in `ActionDispatch::Http::Request#GET` and
+    `ActionDispatch::Http::Request#POST` prior to validating encoding.
 
-    `params[:nested_arrays][0][0].permitted?` will now return `true` instead of `false`.
+    *Adrianna Chang*
 
-    *Steve Hull*
+*   Allow `assert_recognizes` routing assertions to work on mounted root routes.
 
-*   Reset `RAW_POST_DATA` and `CONTENT_LENGTH` request environment between test requests in
-    `ActionController::TestCase` subclasses.
+    *Gannon McGibbon*
 
-    *Eugene Kenny*
+*   Change default redirection status code for non-GET/HEAD requests to 308 Permanent Redirect for `ActionDispatch::SSL`.
 
-*   Output only one Content-Security-Policy nonce header value per request.
+    *Alan Tan*, *Oz Ben-David*
 
-    Fixes #32597.
+*   Fix `follow_redirect!` to follow redirection with same HTTP verb when following
+    a 308 redirection.
 
-    *Andrey Novikov*, *Andrew White*
+    *Alan Tan*
 
-*   Only disable GPUs for headless Chrome on Windows.
+*   When multiple domains are specified for a cookie, a domain will now be
+    chosen only if it is equal to or is a superdomain of the request host.
 
-    It is not necessary anymore for Linux and macOS machines.
+    *Jonathan Hefner*
 
-    https://bugs.chromium.org/p/chromium/issues/detail?id=737678#c1
+*   `ActionDispatch::Static` handles precompiled Brotli (.br) files.
 
-    *Stefan Wrobel*
+    Adds to existing support for precompiled gzip (.gz) files.
+    Brotli files are preferred due to much better compression.
 
-*   Fix system tests transactions not closed between examples.
+    When the browser requests /some.js with `Accept-Encoding: br`,
+    we check for public/some.js.br and serve that file, if present, with
+    `Content-Encoding: br` and `Vary: Accept-Encoding` headers.
 
-    *Sergey Tarasov*
+    *Ryan Edward Hall*, *Jeremy Daer*
 
+*   Add raise_on_missing_translations support for controllers.
 
-## Rails 5.2.0 (April 09, 2018) ##
+    This configuration determines whether an error should be raised for missing translations.
+    It can be enabled through `config.i18n.raise_on_missing_translations`. Note that described
+    configuration also affects raising error for missing translations in views.
 
-*   Check exclude before flagging cookies as secure.
+    *fatkodima*
 
-    *Catherine Khuu*
+*   Added `compact` and `compact!` to `ActionController::Parameters`.
 
-*   Always yield a CSP policy instance from `content_security_policy`
+    *Eugene Kenny*
 
-    This allows a controller action to enable the policy individually
-    for a controller and/or specific actions.
+*   Calling `each_pair` or `each_value` on an `ActionController::Parameters`
+    without passing a block now returns an enumerator.
 
-    *Andrew White*
+    *Eugene Kenny*
 
-*   Add the ability to disable the global CSP in a controller, e.g:
+*   `fixture_file_upload` now uses path relative to `file_fixture_path`
 
-        class LegacyPagesController < ApplicationController
-          content_security_policy false, only: :index
-        end
+    Previously the path had to be relative to `fixture_path`.
+    You can change your existing code as follow:
 
-    *Andrew White*
+    ```ruby
+    # Before
+    fixture_file_upload('files/dog.png')
 
-*   Add alias method `to_hash` to `to_h` for `cookies`.
-    Add alias method `to_h` to `to_hash` for `session`.
+    # After
+    fixture_file_upload('dog.png')
+    ```
 
-    *Igor Kasyanchuk*
+    *Edouard Chin*
 
-*   Update the default HSTS max-age value to 31536000 seconds (1 year)
-    to meet the minimum max-age requirement for https://hstspreload.org/.
+*   Remove deprecated `force_ssl` at the controller level.
 
-    *Grant Bourque*
+    *Rafael Mendonça França*
 
-*   Add support for automatic nonce generation for Rails UJS.
+*   The +helper+ class method for controllers loads helper modules specified as
+    strings/symbols with `String#constantize` instead of `require_dependency`.
 
-    Because the UJS library creates a script tag to process responses it
-    normally requires the script-src attribute of the content security
-    policy to include 'unsafe-inline'.
+    Remember that support for strings/symbols is only a convenient API. You can
+    always pass a module object:
 
-    To work around this we generate a per-request nonce value that is
-    embedded in a meta tag in a similar fashion to how CSRF protection
-    embeds its token in a meta tag. The UJS library can then read the
-    nonce value and set it on the dynamically generated script tag to
-    enable it to execute without needing 'unsafe-inline' enabled.
+    ```ruby
+    helper UtilsHelper
+    ```
 
-    Nonce generation isn't 100% safe - if your script tag is including
-    user generated content in someway then it may be possible to exploit
-    an XSS vulnerability which can take advantage of the nonce. It is
-    however an improvement on a blanket permission for inline scripts.
+    which is recommended because it is simple and direct. When a string/symbol
+    is received, `helper` just manipulates and inflects the argument to obtain
+    that same module object.
 
-    It is also possible to use the nonce within your own script tags by
-    using `nonce: true` to set the nonce value on the tag, e.g
+    *Xavier Noria*, *Jean Boussier*
 
-        <%= javascript_tag nonce: true do %>
-          alert('Hello, World!');
-        <% end %>
+*   Correctly identify the entire localhost IPv4 range as trusted proxy.
 
-    Fixes #31689.
+    *Nick Soracco*
 
-    *Andrew White*
+*   `url_for` will now use "https://" as the default protocol when
+    `Rails.application.config.force_ssl` is set to true.
 
-*   Matches behavior of `Hash#each` in `ActionController::Parameters#each`.
+    *Jonathan Hefner*
 
-    Rails 5.0 introduced a bug when looping through controller params using `each`. Only the keys of params hash were passed to the block, e.g.
+*   Accept and default to base64_urlsafe CSRF tokens.
 
-        # Parameters: {"param"=>"1", "param_two"=>"2"}
-        def index
-          params.each do |name|
-            puts name
-          end
-        end
+    Base64 strict-encoded CSRF tokens are not inherently websafe, which makes
+    them difficult to deal with. For example, the common practice of sending
+    the CSRF token to a browser in a client-readable cookie does not work properly
+    out of the box: the value has to be url-encoded and decoded to survive transport.
 
-        # Prints
-        # param
-        # param_two
+    Now, we generate Base64 urlsafe-encoded CSRF tokens, which are inherently safe
+    to transport. Validation accepts both urlsafe tokens, and strict-encoded tokens
+    for backwards compatibility.
 
-    In Rails 5.2 the bug has been fixed and name will be an array (which was the behavior for all versions prior to 5.0), instead of a string.
+    *Scott Blum*
 
-    To fix the code above simply change as per example below:
+*   Support rolling deploys for cookie serialization/encryption changes.
 
-        # Parameters: {"param"=>"1", "param_two"=>"2"}
-        def index
-          params.each do |name, value|
-            puts name
-          end
-        end
+    In a distributed configuration like rolling update, users may observe
+    both old and new instances during deployment. Users may be served by a
+    new instance and then by an old instance.
 
-        # Prints
-        # param
-        # param_two
+    That means when the server changes `cookies_serializer` from `:marshal`
+    to `:hybrid` or the server changes `use_authenticated_cookie_encryption`
+    from `false` to `true`, users may lose their sessions if they access the
+    server during deployment.
 
-    *Dominic Cleal*
+    We added fallbacks to downgrade the cookie format when necessary during
+    deployment, ensuring compatibility on both old and new instances.
 
-*   Add `Referrer-Policy` header to default headers set.
+    *Masaki Hara*
 
-    *Guillermo Iguaran*
+*   `ActionDispatch::Request.remote_ip` has ip address even when all sites are trusted.
 
-*   Changed the system tests to set Puma as default server only when the
-    user haven't specified manually another server.
+    Before, if all `X-Forwarded-For` sites were trusted, the `remote_ip` would default to `127.0.0.1`.
+    Now, the furthest proxy site is used. e.g.: It now gives an ip address when using curl from the load balancer.
 
-    *Guillermo Iguaran*
+    *Keenan Brock*
 
-*   Add secure `X-Download-Options` and `X-Permitted-Cross-Domain-Policies` to
-    default headers set.
+*   Fix possible information leak / session hijacking vulnerability.
 
-    *Guillermo Iguaran*
+    The `ActionDispatch::Session::MemcacheStore` is still vulnerable given it requires the
+    gem dalli to be updated as well.
 
-*   Add headless firefox support to System Tests.
+    CVE-2019-16782.
 
-    *bogdanvlviv*
+*   Include child session assertion count in ActionDispatch::IntegrationTest.
 
-*   Changed the default system test screenshot output from `inline` to `simple`.
+    `IntegrationTest#open_session` uses `dup` to create the new session, which
+    meant it had its own copy of `@assertions`. This prevented the assertions
+    from being correctly counted and reported.
 
-    `inline` works well for iTerm2 but not everyone uses iTerm2. Some terminals like
-    Terminal.app ignore the `inline` and output the path to the file since it can't
-    render the image. Other terminals, like those on Ubuntu, cannot handle the image
-    inline, but also don't handle it gracefully and instead of outputting the file
-    path, it dumps binary into the terminal.
+    Child sessions now have their `attr_accessor` overridden to delegate to the
+    root session.
 
-    Commit 9d6e28 fixes this by changing the default for screenshot to be `simple`.
+    Fixes #32142.
 
-    *Eileen M. Uchitelle*
+    *Sam Bostock*
 
-*   Register most popular audio/video/font mime types supported by modern browsers.
+*   Add SameSite protection to every written cookie.
 
-    *Guillermo Iguaran*
+    Enabling `SameSite` cookie protection is an addition to CSRF protection,
+    where cookies won't be sent by browsers in cross-site POST requests when set to `:lax`.
 
-*   Fix optimized url helpers when using relative url root.
+    `:strict` disables cookies being sent in cross-site GET or POST requests.
 
-    Fixes #31220.
+    Passing `:none` disables this protection and is the same as previous versions albeit a `; SameSite=None` is appended to the cookie.
 
-    *Andrew White*
+    See upgrade instructions in config/initializers/new_framework_defaults_6_1.rb.
 
-*   Add DSL for configuring Content-Security-Policy header.
+    More info [here](https://tools.ietf.org/html/draft-west-first-party-cookies-07)
 
-    The DSL allows you to configure a global Content-Security-Policy
-    header and then override within a controller. For more information
-    about the Content-Security-Policy header see MDN:
+    _NB: Technically already possible as Rack supports SameSite protection, this is to ensure it's applied to all cookies_
 
-    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
+    *Cédric Fabianski*
 
-    Example global policy:
+*   Bring back the feature that allows loading external route files from the router.
 
-        # config/initializers/content_security_policy.rb
-        Rails.application.config.content_security_policy do |p|
-          p.default_src :self, :https
-          p.font_src    :self, :https, :data
-          p.img_src     :self, :https, :data
-          p.object_src  :none
-          p.script_src  :self, :https
-          p.style_src   :self, :https, :unsafe_inline
-        end
+    This feature existed back in 2012 but got reverted with the incentive that
+    https://github.com/rails/routing_concerns was a better approach. Turned out
+    that this wasn't fully the case and loading external route files from the router
+    can be helpful for applications with a really large set of routes.
+    Without this feature, application needs to implement routes reloading
+    themselves and it's not straightforward.
 
-    Example controller overrides:
+    ```ruby
+    # config/routes.rb
 
-        # Override policy inline
-        class PostsController < ApplicationController
-          content_security_policy do |p|
-            p.upgrade_insecure_requests true
-          end
-        end
+    Rails.application.routes.draw do
+      draw(:admin)
+    end
 
-        # Using literal values
-        class PostsController < ApplicationController
-          content_security_policy do |p|
-            p.base_uri "https://www.example.com"
-          end
-        end
+    # config/routes/admin.rb
 
-        # Using mixed static and dynamic values
-        class PostsController < ApplicationController
-          content_security_policy do |p|
-            p.base_uri :self, -> { "https://#{current_user.domain}.example.com" }
-          end
-        end
+    get :foo, to: 'foo#bar'
+    ```
 
-    Allows you to also only report content violations for migrating
-    legacy content using the `content_security_policy_report_only`
-    configuration attribute, e.g;
+    *Yehuda Katz*, *Edouard Chin*
 
-        # config/initializers/content_security_policy.rb
-        Rails.application.config.content_security_policy_report_only = true
+*   Fix system test driver option initialization for non-headless browsers.
 
-        # controller override
-        class PostsController < ApplicationController
-          content_security_policy_report_only only: :index
-        end
+    *glaszig*
 
-    Note that this feature does not validate the header for performance
-    reasons since the header is calculated at runtime.
+*   `redirect_to.action_controller` notifications now include the `ActionDispatch::Request` in
+    their payloads as `:request`.
 
-    *Andrew White*
+    *Austin Story*
 
-*   Make `assert_recognizes` to traverse mounted engines.
+*   `respond_to#any` no longer returns a response's Content-Type based on the
+    request format but based on the block given.
 
-    *Yuichiro Kaneko*
+    Example:
 
-*   Remove deprecated `ActionController::ParamsParser::ParseError`.
+    ```ruby
+      def my_action
+        respond_to do |format|
+          format.any { render(json: { foo: 'bar' }) }
+        end
+      end
 
-    *Rafael Mendonça França*
+      get('my_action.csv')
+    ```
 
-*   Add `:allow_other_host` option to `redirect_back` method.
+    The previous behaviour was to respond with a `text/csv` Content-Type which
+    is inaccurate since a JSON response is being rendered.
 
-    When `allow_other_host` is set to `false`, the `redirect_back` will not allow redirecting from a
-    different host. `allow_other_host` is `true` by default.
+    Now it correctly returns a `application/json` Content-Type.
 
-    *Tim Masliuchenko*
+    *Edouard Chin*
 
-*   Add headless chrome support to System Tests.
+*   Replaces (back)slashes in failure screenshot image paths with dashes.
 
-    *Yuji Yaginuma*
+    If a failed test case contained a slash or a backslash, a screenshot would be created in a
+    nested directory, causing issues with `tmp:clear`.
 
-*   Add ability to enable Early Hints for HTTP/2
+    *Damir Zekic*
 
-    If supported by the server, and enabled in Puma this allows H2 Early Hints to be used.
+*   Add `params.member?` to mimic Hash behavior.
 
-    The `javascript_include_tag` and the `stylesheet_link_tag` automatically add Early Hints if requested.
+    *Younes Serraj*
 
-    *Eileen M. Uchitelle*, *Aaron Patterson*
+*   `process_action.action_controller` notifications now include the following in their payloads:
 
-*   Simplify cookies middleware with key rotation support
+    * `:request` - the `ActionDispatch::Request`
+    * `:response` - the `ActionDispatch::Response`
 
-    Use the `rotate` method for both `MessageEncryptor` and
-    `MessageVerifier` to add key rotation support for encrypted and
-    signed cookies. This also helps simplify support for legacy cookie
-    security.
+    *George Claghorn*
 
-    *Michael J Coyne*
+*   Updated `ActionDispatch::Request.remote_ip` setter to clear set the instance
+    `remote_ip` to `nil` before setting the header that the value is derived
+    from.
 
-*   Use Capybara registered `:puma` server config.
+    Fixes #37383.
 
-    The Capybara registered `:puma` server ensures the puma server is run in process so
-    connection sharing and open request detection work correctly by default.
+    *Norm Provost*
 
-    *Thomas Walpole*
+*   `ActionController::Base.log_at` allows setting a different log level per request.
 
-*   Cookies `:expires` option supports `ActiveSupport::Duration` object.
+    ```ruby
+    # Use the debug level if a particular cookie is set.
+    class ApplicationController < ActionController::Base
+      log_at :debug, if: -> { cookies[:debug] }
+    end
+    ```
 
-        cookies[:user_name] = { value: "assain", expires: 1.hour }
-        cookies[:key] = { value: "a yummy cookie", expires: 6.months }
+    *George Claghorn*
 
-    Pull Request: #30121
+*   Allow system test screen shots to be taken more than once in
+    a test by prefixing the file name with an incrementing counter.
 
-    *Assain Jaleel*
+    Add an environment variable `RAILS_SYSTEM_TESTING_SCREENSHOT_HTML` to
+    enable saving of HTML during a screenshot in addition to the image.
+    This uses the same image name, with the extension replaced with `.html`
 
-*   Enforce signed/encrypted cookie expiry server side.
+    *Tom Fakes*
 
-    Rails can thwart attacks by malicious clients that don't honor a cookie's expiry.
+*   Add `Vary: Accept` header when using `Accept` header for response.
 
-    It does so by stashing the expiry within the written cookie and relying on the
-    signing/encrypting to vouch that it hasn't been tampered with. Then on a
-    server-side read, the expiry is verified and any expired cookie is discarded.
+    For some requests like `/users/1`, Rails uses requests' `Accept`
+    header to determine what to return. And if we don't add `Vary`
+    in the response header, browsers might accidentally cache different
+    types of content, which would cause issues: e.g. javascript got displayed
+    instead of html content. This PR fixes these issues by adding `Vary: Accept`
+    in these types of requests. For more detailed problem description, please read:
 
-    Pull Request: #30121
+    https://github.com/rails/rails/pull/36213
 
-    *Assain Jaleel*
+    Fixes #25842.
 
-*   Make `take_failed_screenshot` work within engine.
+    *Stan Lo*
 
-    Fixes #30405.
+*   Fix IntegrationTest `follow_redirect!` to follow redirection using the same HTTP verb when following
+    a 307 redirection.
 
-    *Yuji Yaginuma*
+    *Edouard Chin*
 
-*   Deprecate `ActionDispatch::TestResponse` response aliases.
+*   System tests require Capybara 3.26 or newer.
 
-    `#success?`, `#missing?` & `#error?` are not supported by the actual
-    `ActionDispatch::Response` object and can produce false-positives. Instead,
-    use the response helpers provided by `Rack::Response`.
+    *George Claghorn*
 
-    *Trevor Wistaff*
+*   Reduced log noise handling ActionController::RoutingErrors.
 
-*   Protect from forgery by default
+    *Alberto Fernández-Capel*
 
-    Rather than protecting from forgery in the generated `ApplicationController`,
-    add it to `ActionController::Base` depending on
-    `config.action_controller.default_protect_from_forgery`. This configuration
-    defaults to false to support older versions which have removed it from their
-    `ApplicationController`, but is set to true for Rails 5.2.
+*   Add DSL for configuring HTTP Feature Policy.
 
-    *Lisa Ugray*
+    This new DSL provides a way to configure an HTTP Feature Policy at a
+    global or per-controller level. Full details of HTTP Feature Policy
+    specification and guidelines can be found at MDN:
 
-*   Fallback `ActionController::Parameters#to_s` to `Hash#to_s`.
+    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
 
-    *Kir Shatrov*
+    Example global policy:
 
-*   `driven_by` now registers poltergeist and capybara-webkit.
+    ```ruby
+    Rails.application.config.feature_policy do |f|
+      f.camera      :none
+      f.gyroscope   :none
+      f.microphone  :none
+      f.usb         :none
+      f.fullscreen  :self
+      f.payment     :self, "https://secure.example.com"
+    end
+    ```
 
-    If poltergeist or capybara-webkit are set as drivers is set for System Tests,
-    `driven_by` will register the driver and set additional options passed via
-    the `:options` parameter.
+    Example controller level policy:
 
-    Refer to the respective driver's documentation to see what options can be passed.
+    ```ruby
+    class PagesController < ApplicationController
+      feature_policy do |p|
+        p.geolocation "https://example.com"
+      end
+    end
+    ```
 
-    *Mario Chavez*
+    *Jacob Bednarz*
 
-*   AEAD encrypted cookies and sessions with GCM.
+*   Add the ability to set the CSP nonce only to the specified directives.
 
-    Encrypted cookies now use AES-GCM which couples authentication and
-    encryption in one faster step and produces shorter ciphertexts. Cookies
-    encrypted using AES in CBC HMAC mode will be seamlessly upgraded when
-    this new mode is enabled via the
-    `action_dispatch.use_authenticated_cookie_encryption` configuration value.
+    Fixes #35137.
 
-    *Michael J Coyne*
+    *Yuji Yaginuma*
 
-*   Change the cache key format for fragments to make it easier to debug key churn. The new format is:
+*   Keep part when scope option has value.
 
-        views/template/action.html.erb:7a1156131a6928cb0026877f8b749ac9/projects/123
-              ^template path           ^template tree digest            ^class   ^id
+    When a route was defined within an optional scope, if that route didn't
+    take parameters the scope was lost when using path helpers. This commit
+    ensures scope is kept both when the route takes parameters or when it
+    doesn't.
 
-    *DHH*
+    Fixes #33219.
 
-*   Add support for recyclable cache keys with fragment caching. This uses the new versioned entries in the
-    `ActiveSupport::Cache` stores and relies on the fact that Active Record has split `#cache_key` and `#cache_version`
-    to support it.
+    *Alberto Almagro*
 
-    *DHH*
+*   Added `deep_transform_keys` and `deep_transform_keys!` methods to ActionController::Parameters.
 
-*   Add `action_controller_api` and `action_controller_base` load hooks to be called in `ActiveSupport.on_load`
+    *Gustavo Gutierrez*
 
-    `ActionController::Base` and `ActionController::API` have differing implementations. This means that
-    the one umbrella hook `action_controller` is not able to address certain situations where a method
-    may not exist in a certain implementation.
+*   Calling `ActionController::Parameters#transform_keys`/`!` without a block now returns
+    an enumerator for the parameters instead of the underlying hash.
 
-    This is fixed by adding two new hooks so you can target `ActionController::Base` vs `ActionController::API`
+    *Eugene Kenny*
 
-    Fixes #27013.
+*   Fix strong parameters blocks all attributes even when only some keys are invalid (non-numerical).
+    It should only block invalid key's values instead.
 
-    *Julian Nadeau*
+    *Stan Lo*
 
 
-Please check [5-1-stable](https://github.com/rails/rails/blob/5-1-stable/actionpack/CHANGELOG.md) for previous changes.
+Please check [6-0-stable](https://github.com/rails/rails/blob/6-0-stable/actionpack/CHANGELOG.md) for previous changes.