[
https://issues.apache.org/jira/browse/WICKET-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051967#comment-13051967
]
Ivan Vasilev commented on WICKET-3817:
--------------------------------------
The problem was the browser cache indeed. Thanks and sorry for the false
warning.
> JavaScript compression and Https
> --------------------------------
>
> Key: WICKET-3817
> URL: https://issues.apache.org/jira/browse/WICKET-3817
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC5
> Reporter: Ivan Vasilev
> Assignee: Peter Ertl
> Attachments: quickstart_javascript_compression.rar
>
>
> There is a wicket application (in deployment mode) with https configured over
> some pages. When a javascript resource is retrieved via https, the resource
> is compressed. However if the same resource is retrieved via http, no
> compression occurs.
> In the attached quickstart there are two pages (https://localhost/h and
> http://localhost/h2) and the same javascript resource is included in both. In
> the https page the resources is compressed and in the http page it's not.
> Also, I'd like to ask (following the discussion in
> https://issues.apache.org/jira/browse/WICKET-3674) is it safe to use the
> javascript compressor for css? Thanks.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
