[jira] [Resolved] (WICKET-4283) Use MSXMLHTTP ProgID lookup Check for MSXML http ajax objects for IE

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4283.
-------------------------------------

    Resolution: Won't Fix

Closing as "Won't Fix" - Wicket 6 uses jQuery to deal with Ajax request handling.
                
> Use MSXMLHTTP ProgID lookup Check for MSXML http ajax objects for IE
> --------------------------------------------------------------------
>
>                 Key: WICKET-4283
>                 URL: https://issues.apache.org/jira/browse/WICKET-4283
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.4.19
>         Environment: Windows7, WindowsXP, Tomcat all versions, Internet Explorer 7, 8, 9.
>            Reporter: Berlin Brown
>            Priority: Minor
>              Labels: IE, xhr,, xmlhttp,
>         Attachments: WicketAjaxFORieAjax.patch
>
>
> The IE team and MSXML team and also other client side oriented frameworks(see jQuery) are using a MSXML lookup for the ajax XHR transport object.  Wicket 1.4.x versions are using the legacy new ActiveXObject("Microsoft.XMLHTTP") object.  Some browsers may disable the object and may cause issues for ajax requests.
> http://blogs.msdn.com/b/xmlteam/archive/2006/10/23/using-the-right-version-of-msxml-in-internet-explorer.aspx
> I guess using a simple lookup for the MSXML object.  The standard seems to be: Msxml2.XMLHTTP  but, you may also lookup Msxml2.XMLHTTP.6.0  for IE8  and above.
> Using the right XHR object may add security and performance fixes provided by IE.  The legacy Microsoft.XMLHTTP object is not recommended.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira