Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Distributed network, about 600 PCs, just upgraded to IE8.

Currently the 'Enable Native XMLHTTP Support' option is disabled (perhaps this is an artifact of the upgrade from IE7) but its causing a few very specific problems with certain jquery widgets etc.

Is there any good reason not to turn this option on?

edit: This explains the setting for IE7 (when it was introduced):
MSDN: About Native XMLHTTP

share|improve this question

Alas some paranoid organisations set this policy on believing that the native XMLHttpRequest object presents a security risk. For most (all?) circumstances, this setting shouldn't be set as it will break contemporary applications. However, when you're faced with paranoid "security" people who just say "no", it can be a significant political challenge to get this policy reversed.

Example: Oracle ADF won't work if this setting is on:

share|improve this answer

In IE 8, it does not use XMLHttpRequest(), but falls back on ActiveXObject("Msxml2.XMLHTTP"). See here for explanation.

If the native support is causing issues and the code calls the former, it may require disabling to get the code to pass through that choice and select the latter to work (assuming the coder has included both options in a try...catch scenario, like at the site, above).

On the other hand, disabling it can break AJAX if apps were written with IE 7/FF/Chrome in mind, where they were using XMLHttpRequest or are using jQuery $.ajax() calls.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.