[
https://issues.apache.org/jira/browse/WICKET-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781844#comment-13781844
]
Martin Grigorov commented on WICKET-5372:
-----------------------------------------
Wicket doesn't require the end user to change its registry.
Wicket just sets a sane default headers.
The application developer can change all default headers to anything that is
appropriate for her application functionality.
The framework doesn't know that a file will be streamed to a client with IE8
browser and there is a bug in this specific browser or version of this browser.
Please paste the stacktrace when
org.apache.wicket.request.http.WebResponse#disableCaching() is called. Let's
see why caching is disabled in first place.
> Cache Disable Headers Break IE8 Under HTTPS
> -------------------------------------------
>
> Key: WICKET-5372
> URL: https://issues.apache.org/jira/browse/WICKET-5372
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.9.0
> Reporter: Brandon Fuller
> Priority: Minor
>
> I am serving up a non-cached PDF resource from Wicket with:
> getRequestCycle().scheduleRequestHandlerAfterCurrent(new
> ResourceRequestHandler(pdfResource, null));
> All is fine for most users. However, our IE8 users cannot perform the
> download. The get a dialog saying that the resource cannot be downloaded. I
> did some testing and found that it works fine over HTTP but not HTTPS.
> I found this stack overflow article that explains:
> http://stackoverflow.com/questions/1038707/cant-display-pdf-from-https-in-ie-8-on-64-bit-vista
> I see in WebResponse that Wicket is setting the Cache-Control and Pragma
> values incorrectly as far as IE8 is concerned. This explains the behavior.
> To prove, I changed the resource in wicket to have a cache duration of one
> second and the resource downloads over SSL just fine. Not the worst
> workaround but I was hoping this could be addressed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
