[jira] Closed: (TAP5-917) Don't set Expires header when tapestry.production-mode is false

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-917.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> Don't set Expires header when tapestry.production-mode is false
> ---------------------------------------------------------------
>
>                 Key: TAP5-917
>                 URL: https://issues.apache.org/jira/browse/TAP5-917
>             Project: Tapestry 5
>          Issue Type: Improvement
>            Reporter: Louis Marascio
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> When running Tapestry with tapestry.production-mode set to false, the Expires header is set to requestTime + 10 years. I know this behavior is desired for long lived assets, but in development mode it tends to cause problems with designers as they work on assets outside of the classpath. Ideally, during development, the Expires header would never be set. It would be nice if this behavior were controlled by a configuration setting if it isn't desirable to tie it to tapestry.production-mode.

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