[
https://issues.apache.org/jira/browse/TAP5-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403645#comment-13403645
]
Howard M. Lewis Ship commented on TAP5-1964:
--------------------------------------------
Thanks for Robert Lentz for all the detective work!
> In production mode, placeholder timestamp needs to be limited to one-second
> accuracy
> ------------------------------------------------------------------------------------
>
> Key: TAP5-1964
> URL: https://issues.apache.org/jira/browse/TAP5-1964
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.3, 5.4
> Reporter: Howard M. Lewis Ship
>
> In production mode, Tapestry turns off the logic that checks for changes to
> files (all types of files, including resources made available as assets). It
> uses a single placeholder value to identify the date time modified of all
> resources.
> When a request for a resource is sent from the client, the time stamp in the
> request is compared to the placeholder timestamp. Unfortunately, in most
> cases, they are not equal as expected, because the date on the client is one
> one-second accurate, not millisecond accurate.
> The end result is many more asset requests are processed fully, rather than
> sending a 304 result code.
> The fix is to limit the placeholder time stamp value to one second accuracy,
> so that the server and the client can agree that the client has the up-to
> date version of the asset.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
