Comments on: Firefox 1.5, XmlHttpRequest, req.responseXML and document.domain http://alexander.kirk.at/2006/07/27/firefox-15-xmlhttprequest-reqresponsexml-and-documentdomain/ Tue, 23 Feb 2010 01:32:11 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Thomas Einwaller http://alexander.kirk.at/2006/07/27/firefox-15-xmlhttprequest-reqresponsexml-and-documentdomain/comment-page-1/#comment-4085 Thomas Einwaller Mon, 31 Jul 2006 16:23:08 +0000 http://alexander.kirk.at/?p=63#comment-4085 This IS a Firefox bug. Though the repsonse content type is set to "text/xml" Firefox does not allow you to access responseXML if document.domain is set. I tried overrideMimeType("text/xml") too but that did not help. The only thing that works is to parse the xml again like kirk describes it. This IS a Firefox bug. Though the repsonse content type is set to "text/xml" Firefox does not allow you to access responseXML if document.domain is set.

I tried overrideMimeType("text/xml") too but that did not help.

The only thing that works is to parse the xml again like kirk describes it.

]]> By: kourge http://alexander.kirk.at/2006/07/27/firefox-15-xmlhttprequest-reqresponsexml-and-documentdomain/comment-page-1/#comment-4042 kourge Sat, 29 Jul 2006 23:21:04 +0000 http://alexander.kirk.at/?p=63#comment-4042 The responseXML "bug" in Firefox isn't a bug. As <a href="http://developer.mozilla.org/en/docs/AJAX:Getting_Started" rel="nofollow">stated in the MDC</a>, Mozilla browsers will not make the responseXML available unless the server serves the MIME type text/xml. There are two ways to fix this. One is to alter the server's script to make it serve the Content-Type: text/xml header. The second way is to do something like this in your JavaScript code: if (window.XMLHttpRequest) { req = new XMLHttpRequest(); if (req.overrideMimeType) req.overrideMimeType("text/xml"); } else if (window.ActiveXObject) { req = new ActiveXObject("Microsoft.XMLHTTP"); } This will force Mozilla browsers to parse the responded XML in the XMLHttpRequest object, given that the XML is well-formed. The responseXML "bug" in Firefox isn't a bug. As stated in the MDC, Mozilla browsers will not make the responseXML available unless the server serves the MIME type text/xml.
There are two ways to fix this. One is to alter the server's script to make it serve the Content-Type: text/xml header. The second way is to do something like this in your JavaScript code:
if (window.XMLHttpRequest) {
req = new XMLHttpRequest();
if (req.overrideMimeType) req.overrideMimeType("text/xml");
} else if (window.ActiveXObject) {
req = new ActiveXObject("Microsoft.XMLHTTP");
}
This will force Mozilla browsers to parse the responded XML in the XMLHttpRequest object, given that the XML is well-formed.

]]> By: Ajaxian » Pains of document.domain in FireFox 1.5 http://alexander.kirk.at/2006/07/27/firefox-15-xmlhttprequest-reqresponsexml-and-documentdomain/comment-page-1/#comment-3959 Ajaxian » Pains of document.domain in FireFox 1.5 Thu, 27 Jul 2006 18:55:45 +0000 http://alexander.kirk.at/?p=63#comment-3959 [...] Alexander Kirk has written about a problem with XHR, responseXML and document.domain in FireFox: [...] [...] Alexander Kirk has written about a problem with XHR, responseXML and document.domain in FireFox: [...]

]]>