Tapestry 5
  1. Tapestry 5
  2. TAP5-917

Don't set Expires header when tapestry.production-mode is false

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2.0
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Louis Marascio
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development