-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difference in GM_xhr responseHeaders between FF 5.1.1 and Chrome 5.2.3 #2160
Comments
Observe the same behaviour. |
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 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
.The text was updated successfully, but these errors were encountered: