There is No Warning When The Option 'Enable native XMLHTTP support' is not Selected in Internet Explorer (Doc ID 1114935.1)

Last updated on AUGUST 04, 2016

Applies to:

Oracle JDeveloper - Version: 11.1.1.2.0 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

When running ADF applications in Internet Explorer, problems will occur when the browser setting Enable native XMLHTTP support is turned off.

According to the following blog:

Script For Detecting Availability of XMLHttp in Internet Explorer
http://blogs.oracle.com/groundside/2010/05/script_for_detecting_availability_of_xmlhttp_in_internet_explorer.html

It states:

Having the XMLHttpRequest API available is key to any ADF Faces Rich Client application.
Without XMLHttpRequest available, your ADF Faces application will simply not work correctly.

Unfortunately, it is possible for users to switch off this option in Internet Explorer as a Security setting..
It allows users to turn off this setting without knowing the full implication or affects it will have on their application, which in turn when de-selected can cause major problems.

There does not seem to be any warning to users warning or stating the full implications of having the option Enable native XMLHTTP support disabled.

Simple Testcase

Here we will show a simple scenario on what can happen when Enable native XMLHTTP support is disabled.
  • At this stage Enable native XMLHTTP support is enabled.
  • Run a JSPX page that contains ADF components i.e. Panel Accordion, Panel Tabbed, menus etc.
  • When the application is running in Internet Explorer perform a function like select an accordion or a tab, where all functionality will work as expected.

    Cause

    Sign In with your My Oracle Support account

    Don't have a My Oracle Support account? Click to get started

    My Oracle Support provides customers with access to over a
    Million Knowledge Articles and hundreds of Community platforms