[
https://issues.apache.org/jira/browse/TAPESTRY-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503853
]
Daniel Gredler commented on TAPESTRY-1447:
------------------------------------------
My quick look at this issue suggested that URLChangeTracker tracks changes in
milliseconds, while the HTTP headers like Last-Modified have a granularity of
seconds. This means that when the browser tells T5 "don't give me this file if
it hasn't been modified since...", T5 thinks it *has* been modified, because
its internal timestamp is a couple of hundred milliseconds after the
browser-specified time. I'll try to commit a fix to this granularity mismatch
when I get a chance.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
