Bug #5723
closed
CSRF error on dashboard: Refused to set unsafe header "Content-length"
Added by Pi Ba over 10 years ago.
Updated over 10 years ago.
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
- 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.
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.
- 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.
- % Done changed from 0 to 100
Applied in changeset commit:311e4ad5ea15f8303205b31a2bc4afc868ee9441.
- Status changed from Feedback to Resolved
- Assignee deleted (
Pi Ba)
Also available in: Atom
PDF