Defect #37562

POST Requests to repository WS fail with "Can't verify CSRF token authenticity"

Added by Go MAEDA about 1 month ago. Updated about 1 month ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Go MAEDA% Done:

0%

Category:SCM extra
Target version:5.0.3
Resolution:Fixed Affected version:

Description

The issue has been reported as #33029#note-6 and #33029#note-8.

Started POST "/sys/fetch_changesets" for 127.0.0.1 at 2022-08-09 14:53:41 +0900
Processing by SysController#fetch_changesets as */*
  Parameters: {"key"=>"XXXXXXXX"}
Can't verify CSRF token authenticity.
Completed 422 Unprocessable Entity in 1ms (ActiveRecord: 0.0ms | Allocations: 169)

ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken):

37562.patch Magnifier (1.14 KB) Go MAEDA, 2022-08-09 08:35


Related issues

Related to Redmine - Patch #36317: Set default protect from forgery true Closed

Associated revisions

Revision 21766
Added by Go MAEDA about 1 month ago

POST Requests to repository WS fail with "Can't verify CSRF token authenticity" (#37562).

Patch by Go MAEDA.

Revision 21767
Added by Go MAEDA about 1 month ago

Merged r21766 from trunk to 5.0-stable (#37562).

History

#1 Updated by Go MAEDA about 1 month ago

  • Related to Patch #36317: Set default protect from forgery true added

#2 Updated by Go MAEDA about 1 month ago

Attaching a patch to fix the issue.

#3 Updated by Go MAEDA about 1 month ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the fix. Thank you for reporting the issue.

#4 Updated by Yasuhiro Oguro about 1 month ago

MAEDA-san arigatou gozaimasu.

Regards,

Also available in: Atom PDF