Project

General

Profile

Actions

Bug #5723

closed

CSRF error on dashboard: Refused to set unsafe header "Content-length"

Added by Pi Ba over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Very Low
Assignee:
-
Category:
Dashboard
Target version:
-
Start date:
01/02/2016
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:
All

Description

While viewing the dashboard on pfSense in Chrome the error below is logged to the console:
Probably other places to..

Refused to set unsafe header "Content-length"
CsrfMagic.send csrf-magic.js:44
send
jquery-1.11.2.min.js:4
m.extend.ajax jquery-1.11.2.min.js:4
get_gw_stats
(index):835

Actions #1

Updated by Anonymous over 9 years ago

  • Priority changed from Low to Very Low

This is a harmless warning that has been reported already. We may address it at a later date, but for now just ignore it.

Actions #2

Updated by Pi Ba over 9 years ago

Couldn't find the other report (i did search for it.). So just for sake of registration i put it here. And as the browser does 'log' it as an 'error' every few seconds, i think its worth fixing some day. Prio 'very low' is ok for me though.

Actions #3

Updated by Anonymous over 9 years ago

  • Status changed from New to Feedback
  • Assignee set to Pi Ba

Code that sets header length commented out in csrf-magic.js
Error message no longer appears on the browser console, and nothing seems to have broken.

Please report ASAP if you see any GUI issues with this change.

Actions #4

Updated by Anonymous over 9 years ago

  • % Done changed from 0 to 100
Actions #5

Updated by Anonymous over 9 years ago

  • Status changed from Feedback to Resolved
  • Assignee deleted (Pi Ba)
Actions

Also available in: Atom PDF