[jira] Commented: (TAPESTRY-1447) Headers are not set appropiately to allow the browser to cache javascript resources.

["Yann Ramin (JIRA)" <de...@tapestry.apache.org>]

    [ https://issues.apache.org/jira/browse/TAPESTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503760 ] 

Yann Ramin commented on TAPESTRY-1447:
--------------------------------------

It appears that the Resource objects are getting an incorrect Last-Modified header set in the latest snapshot from SVN. 

Hacking ResourceStreamerImpl to use System.currentTimeMillis() when lastModified == 0, and a suitable change in AssetDispatcher.java (to send not modified even when lastmodified == 0) is an ugly workaround but appears to solve the issue.

> Headers are not set appropiately to allow the browser to cache javascript resources.
> ------------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1447
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1447
>             Project: Tapestry
>          Issue Type: Bug
>    Affects Versions: 5.0.4
>            Reporter: Yann Ramin
>            Assignee: Daniel Gredler
>            Priority: Minor
>
> It seems the T5 asset javascript files (such as prototype,scriptalicous) are not being cached by browsers (tested IE6 and FF).
> Using Firebug and having the server on a slow (= cable modem upload)
> connection shows this problem very well (constant reloading of .js and .css files), with about 2-3s page delay in transferring the .js files. Caching appears to work just fine on application images though, which are also injected via assets (the red fieldmarker X is not cached however).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org