Project

General

Profile

Actions

Patch #36317

closed

Set default protect from forgery true

Patch #36317: Set default protect from forgery true

Added by Takashi Kato almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Rails support
Target version:

Description

In Rails 5.2 and later, the default is to raise an exception for invalid CSRF tokens, and there is a configuration for that.

https://github.com/rails/rails/blob/6-1-stable/railties/lib/rails/application/configuration.rb#L123

In Rails 7 and later, the current implementation causes a Deprecation Warning.


Files


Related issues 3 (0 open — 3 closed)

Related to Redmine - Feature #36320: Migrate to Rails 7.2ClosedMarius BĂLTEANUActions
Related to Redmine - Defect #37030: Requests fail with "Can't verify CSRF token authenticity" in mail handlerClosedMarius BĂLTEANUActions
Related to Redmine - Defect #37562: POST Requests to repository WS fail with "Can't verify CSRF token authenticity"ClosedGo MAEDAActions

Updated by Go MAEDA almost 5 years ago Actions #1

  • Target version set to Candidate for next major release

Updated by Go MAEDA almost 5 years ago Actions #2

Updated by Marius BĂLTEANU almost 5 years ago Actions #3

  • Assignee set to Marius BĂLTEANU

Updated by Marius BĂLTEANU almost 5 years ago Actions #4

  • Status changed from New to Closed
  • Target version changed from Candidate for next major release to 5.0.0

Patch committed, thanks!

Updated by Go MAEDA over 4 years ago Actions #5

  • Related to Defect #37030: Requests fail with "Can't verify CSRF token authenticity" in mail handler added

Updated by Go MAEDA over 4 years ago Actions #6

  • Related to Defect #37562: POST Requests to repository WS fail with "Can't verify CSRF token authenticity" added
Actions

Also available in: PDF Atom