Project

General

Profile

Actions

Defect #37562

closed

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

Added by Go MAEDA about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
SCM extra
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
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):

Files

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

Related issues

Related to Redmine - Patch #36317: Set default protect from forgery trueClosedMarius BÄ‚LTEANU

Actions
Actions #1

Updated by Go MAEDA about 2 years ago

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

Updated by Go MAEDA about 2 years ago

Attaching a patch to fix the issue.

Actions #3

Updated by Go MAEDA about 2 years 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.

Actions #4

Updated by Yasuhiro Oguro about 2 years ago

MAEDA-san arigatou gozaimasu.

Regards,

Actions

Also available in: Atom PDF