[jira] [Commented] (TAP5-1717) Assets get cache expiry header of year 1979 in production mode

["Lenny Primak (Commented) (JIRA)" <ji...@apache.org>]

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

Lenny Primak commented on TAP5-1717:
------------------------------------

I traced this down to ResourceChangeTrackerImpl,java line 54...

trackResource always returns timestamp of zero in production mode...

-----------
 public long trackResource(Resource resource)
    {
        if (tracker == null)
        {
            return 0;
        }

        return tracker.add(resource.toURL());
    }


                
> Assets get cache expiry header of year 1979 in production mode
> --------------------------------------------------------------
>
>                 Key: TAP5-1717
>                 URL: https://issues.apache.org/jira/browse/TAP5-1717
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3, 5.4
>            Reporter: Lenny Primak
>            Priority: Critical
>
> Both ContextAssetRequestHandler and StackAssetRequestHandler do not set
> lastModified date correctly in production mode.  They are set to zero,
> which when returned in the browser, the expire header is set to 1979,
> which leads to no assets being cached whatsoever, leading to poor performance.
> This is with yuicompressor enabled.

--
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