Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-4357

Calling WebResponse#enableCaching() is insufficient to enable caching on WebPage (which by default is non-cacheable)

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5.4, 6.0.0-beta1
    • Fix Version/s: 1.5.5, 6.0.0-beta1
    • Component/s: wicket
    • Labels:

      Description

      WebResponse.enableCaching() is documented to enable caching, but it does not. You must also override WebPage.setHeaders(), otherwise it clobbers the headers by calling disableCaching().

      The API docs for WebResponse.enableCaching() should be clear about this.

        Attachments

          Activity

            People

            • Assignee:
              pete Peter Ertl
              Reporter:
              mcallan Michael Allan
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: