You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/04/01 01:58:05 UTC

[jira] [Commented] (TAP5-1114) Response Expires and Last-Modified header attributes for jar entry

    [ https://issues.apache.org/jira/browse/TAP5-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014309#comment-13014309 ] 

Howard M. Lewis Ship commented on TAP5-1114:
--------------------------------------------

Why is this an issue?  Given that Tapestry will create a versioned URL and a far future expires header, what is the problem with the timestamp being for the JAR that contains the resource, rather than the resource itself?

> Response Expires and Last-Modified header attributes for jar entry
> ------------------------------------------------------------------
>
>                 Key: TAP5-1114
>                 URL: https://issues.apache.org/jira/browse/TAP5-1114
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Krishna Caldas
>         Attachments: lastmodified_for_jar_entry.diff, url.jar
>
>
> The response Expires and Last-Modified header attributes for a Jar entry should be related to entry time and not the Jar file last modified date. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira