Bump rails from 5.2.3 to 5.2.6
Bumps rails from 5.2.3 to 5.2.6.
Release notes
Sourced from rails's releases.
5.2.6
Active Support
- No changes.
Active Model
- No changes.
Active Record
- No changes.
Action View
- No changes.
Action Pack
... (truncated)
Accept base64_urlsafe CSRF tokens to make forward compatible.
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.
Atention: If you already upgraded your application to 5.2.5, set the config
urlsafe_csrf_tokens
totrue
, otherwise your form submission will start to fail during the deploy of this new version.Rails.application.config.action_controller.urlsafe_csrf_tokens = true
Commits
-
4866154
Preparing for 5.2.6 release -
4d68f67
Merge branch '5-2-sec' into 5-2-stable -
2612683
Preparing for 5.2.4.6 release -
9df84af
Update changelog -
3d9e9fd
Prevent slow regex when parsing host authorization header -
3eb9e74
Prevent string polymorphic route arguments -
fea508c
Merge pull request #41797 from kamipo/fix_wrong_number_of_arguments_correctly -
4fa8742
Fix "Exception: ActionView::Template::Error: wrong number of arguments (2 for... -
eaf001d
Merge pull request #41806 from kamipo/backport_39076_to_6-0-stable -
767acf6
Fix "Exception: ActionView::Template::Error: wrong number of arguments (2 for... - Additional commits viewable in compare view