2013-02-20 178 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!