Open perpil opened 3 weeks ago
Observe the same behaviour. This breaks some of our logic to parse headers and caused incompatibility.
Should be fixed at 5.3.6209 (crx|xpi in review)
Please download the crx file linked above and drag and drop it to the extensions page chrome://extensions
(after you've enabled 'Developer Mode').
For a quick fix please export your settings and scripts as zip or (JSON) file at the "Utilities" tab and import it back at the fixed BETA version.
Didn't try beta version, not sure how tampermonkey fix this.
Just want to add some context: RFC says HTTP header should always use CRLF as line break.
The
responseHeaders
returned with GM_xmlhttpRequest include\r
in FF TM 5.5.1 and don't in Chrome 5.2.+.This can be worked around, but raising in case it is unintentional.
Expected Behavior
Behavior is consistent across browsers.
Actual Behavior
FF has
\r\n
asresponseHeaders
delimiter, Chrome just has\n
.Specifications
Script
Run this on https://github.com and look in the console in both Firefox and Chrome. Chrome will print
false
, FF will printtrue
.