[
https://issues.apache.org/jira/browse/CLOUDSTACK-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555779#comment-14555779
]
ASF GitHub Bot commented on CLOUDSTACK-8499:
--------------------------------------------
Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/277#issuecomment-104554105
I think it was added to burst caching in browsers when developing the UI.
The fix looks good to me and definitely fixes the issue in a production
deployment but we still need to figure out a way (perhaps in maven client-ui
packaging) to insert ?t=timestamp.
> UI reload perfomance is poor in index.jsp
> -----------------------------------------
>
> Key: CLOUDSTACK-8499
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8499
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, UI
> Affects Versions: 4.6.0, 4.4.4, 4.5.2
> Reporter: Rafael Santos Antunes da Fonseca
> Fix For: 4.6.0, 4.4.4, 4.5.2
>
>
> There is a timestamp being placed in front of some of the static files in
> ui/index.jsp that is preventing tomcat from responding with 304 to the
> client, so that cached client files will not need to be resent.
> This affects page reload speeds harshly.
> This problem affects all versions since 4.0 .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)