2013-02-20 88 views
3

My Firefox just did an update, and now all my XMLHttpRequest (that worked 10 minutes ago) answer in Chinese...Cross-Domain XmlHTTPRequest in chinese after firefox update

I can read this as responseText in firebug :

"㰿硭氠症牳楯渽∱⸰∠敮捯摩涌㴢畴昭ㄶ∿㸍਼㽸浬⵳瑹汥独敥琠瑹灥㴧瑥硴⽸獬✠桲敦㴧⽯扩砯硳扇㼾ഊ㱯扪慭攽≷慑舍㌢⁨牥昽≨瑴瀺⼯ㄲ㜮〮〮ㄺ㠰㠰⽯扩砯睡琐桓敲癞捥⽷慑舍㌯∠楳㴢潢楸㩗慑舍∾ഊ †㱲敬莹浥慭攽≬敡獥∠桲敦㴢汥悭支∠睲楴慢汥㴢玱略∠痴氽≐吵䴢㴢偔こ∠⼾ഊ†㱩湴慭攽≡摤䙲敱略湣礢⁨牥昽≡摤䙲敱略湣礯∠睲楴慢汥㴢玱略∠痴氽∵〰∠浩渽∰∠⼾ഊ†㱯潆湡浥㴢慤搢⁨牥昽≡摤⼢⁩渽≯扩砺坡琐桉沨畴㴢潢楸㩗慑舍并琢 㸍ਠ‼溃慭攽≲敭潶攒⁨牥昽≲敭潶支∠楮㴢潢楸㩗慑舍䥮∠潵琽≯扩砺乩氢 㸍ਠ‼溃慭攽≰潬汃桡涌敳∠桲敦㴢灯汬䍨虑来猯∠楮㴢潢楸㩎楬∠潵琽≯扩砺坡琐桏畴∠⼾ഊ†㱯潆湡浥㴢灯汬剥晲敳柏⁨牥昽≰潬汒敦牥独⼢⁩渽≯扩砺乩氢畴㴢潢楸㩗慑舍并琢 㸍ਠ‼溃慭攽≤敬整攒⁨牥昽≤敬整支∠楮㴢潢楸㩎楬∠潵琽≯扩砺乩氢 㸍ਠ‼溃慭攽≳瑡琢⁨牥昽≳瑡琯∠楮㴢潢楸㩎楬∠潵琽≯扩砺坡琐桓瑡琢 㸍਼⽯扪"

This is fun, but I really would like to have my real answer back.

Do you know if I can change a setting or something?

An important thing to know, is that my ajax code is a crossdomain request. Is it possible that something changed in the http header encoding ?

Thanx a lot !

+1

For information, my Firefox version is 19.0. – 2013-02-20 13:01:10

+0

And in Wireshark evrything seems correct (I have my correct xml). – 2013-02-20 15:26:06

+1

I found now anwser to this, but it seems to be a bug in Firefox 19 in cross-domain ajax calls . I temporary fixed it with downloading the previous version of firefox : [firefox 18 download page](https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/18.0.2/win32/).. . – 2013-02-21 14:48:05

回答

0

Firefox now gives precedence to the UTF-16 BOM over HTTP. This is not a regression but an intentional change. Better not use a UTF-16 BOM if the bytes after it aren't UTF-16!