[ 
https://issues.apache.org/jira/browse/WICKET-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718215#comment-13718215
 ] 

Thomas Heigl edited comment on WICKET-5283 at 7/24/13 10:47 AM:
----------------------------------------------------------------

I'm sorry, I missed one important piece that needs to be in place for this to 
fail. A response header filter that forces IE Edge mode like this:

{code}
        <filter>
                <filter-name>X-UA-Compatible Filter</filter-name>
                <filter-class>com.mycompany.ResponseHeaderFilter</filter-class>
                <init-param>
                        <param-name>headerName</param-name>
                        <param-value>X-UA-Compatible</param-value>
                </init-param>
                <init-param>
                        <param-name>headerValue</param-name>
                        <param-value>IE=edge</param-value>
                </init-param>
        </filter>
        <filter-mapping>
                <filter-name>X-UA-Compatible Filter</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>
{code}

I'm attaching a new quickstart with that filter in place.

I have absolutely no idea how upgrading Wicket could cause this to break. We 
have this logic in place for years and it works until Wicket 6.8.0.

Could you please try once again with the new quickstart?
                
      was (Author: thomas.heigl):
    I'm sorry, I missed one important piece that needs to be in place for this 
to fail. A response header filter that forces IE Edge mode like this:

{quote}
        <filter>
                <filter-name>X-UA-Compatible Filter</filter-name>
                <filter-class>com.mycompany.ResponseHeaderFilter</filter-class>
                <init-param>
                        <param-name>headerName</param-name>
                        <param-value>X-UA-Compatible</param-value>
                </init-param>
                <init-param>
                        <param-name>headerValue</param-name>
                        <param-value>IE=edge</param-value>
                </init-param>
        </filter>
        <filter-mapping>
                <filter-name>X-UA-Compatible Filter</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>
{quote}

I'm attaching a new quickstart with that filter in place.

I have absolutely no idea how upgrading Wicket could cause this to break. We 
have this logic in place for years and it works until Wicket 6.8.0.

Could you please try once again with the new quickstart?
                  
> Problem with uploading files via automatic ajax form submit in IE8
> ------------------------------------------------------------------
>
>                 Key: WICKET-5283
>                 URL: https://issues.apache.org/jira/browse/WICKET-5283
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 6.9.1
>            Reporter: Thomas Heigl
>         Attachments: ie8_onchange_upload_crash.zip
>
>
> When uploading a file via AjaxFormSubmitBehavior("onchange") IE8 hangs with 
> very high CPU usage and does not respond anymore
> This always happens under Windows XP, sometimes on the first, sometimes on 
> the second upload.

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