[
https://issues.apache.org/jira/browse/WICKET-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059984#comment-13059984
]
Sodasmile commented on WICKET-3869:
-----------------------------------
It appears from the Internet Explorer F12 developer tools, network inspector
that the image references from the ajax response may be resolved twice? It
first makes a request for the image URL, initiated by an <img> element, the
request takes < 1ms to complete, with result "(Aborted)", it then makes another
request for the very same image URL, and this time the request completes with
200 OK, and the image is downloaded as expected.
Can it be the case that the ajax response is transferred back to the browser
and the html is evaluated in a different way than earlier, so that Internet
Explorer first tries to resolve the images, then gets interrupted, then tries
another time when the html is properly attached to the DOM tree??
We did not see anything like this when the application was running on 1.4
> ResponseIOException when ajax response contains resource reference
> ------------------------------------------------------------------
>
> Key: WICKET-3869
> URL: https://issues.apache.org/jira/browse/WICKET-3869
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC5.1
> Environment: Internet Explorer
> Reporter: Sodasmile
> Labels: ResponseIOException, explorer, internet
> Attachments: iwicket.zip
>
>
> When ajax response (show modal window) contains shared image response, server
> log reports ResponseIOException.
> See attached example application. Using maven, type mvn package jetty:run.
> Open http://localhost/8080/iwicket/ in Internet Explorer, click the link,
> watch server log (may need to open/close modal window a few times, but
> usually appears on first attempt).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
