Chandan Sethi created WICKET-5216:
-------------------------------------

             Summary: FileUpload: IE9 is not redirecting to response body while 
uploading file using wicket modal page(embedded within a JSP)
                 Key: WICKET-5216
                 URL: https://issues.apache.org/jira/browse/WICKET-5216
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.5.5
            Reporter: Chandan Sethi


In case of IE9 while processing multipart AJAX request we get XMLDocument as 
NULL. So wicket uses its helper JS functions Wicket._htmlToDomDocument() and 
Wicket._createXmlDocument() functions to load XML document. The text used by 
these two methods is of the following form

"- <ajax-response>\r\n- <redirect>\r\n- <![CDATA[ /wicket/page?17\r\n ]]> \r\n 
</redirect>\r\n </ajax-response>"

The function Wicket._htmlToDomDocument() trims the above text and replaces all 
occurrence of ‘/r/n-’. The resultant text (i.e. ‘‘- <ajax-response> <redirect> 
<![CDATA[ /wicket/page?13 ]]> </redirect> </ajax-response>’) is then passed to 
function Wicket._createXmlDocument() for creating XML Document. However 
function Wicket._createXmlDocument() is throwing error as it is unable to load 
XML document from the provided text. Function Wicket._createXmlDocument() gets 
failed to load XML document from text because text has an error i.e. it 
contains extra ‘-’ at the start of the text. Due to the error wicket does not 
found <ajax-response> element in the response. Hence IE9 is not able to process 
the response.

If we remove extra ‘-’ from the text then wicket loads XML document 
successfully and IE9 gets redirect to response successfully.

Note: In case of IE8 we get appropriate XMLDocument therefore wicket does not 
call helper JS functions to get the XML Document. 

--
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

Reply via email to