You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Ertl (Updated) (JIRA)" <ji...@apache.org> on 2012/01/25 20:49:40 UTC

[jira] [Updated] (WICKET-4357) Calling WebResponse#enableCaching() is insufficient to enable caching on WebPage (which by default is non-cacheable)

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

Peter Ertl updated WICKET-4357:
-------------------------------

    Summary: Calling WebResponse#enableCaching() is insufficient to enable caching on WebPage (which by default is non-cacheable)  (was: enableCaching insufficient to enable caching)
    
> Calling WebResponse#enableCaching() is insufficient to enable caching on WebPage (which by default is non-cacheable)
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-4357
>                 URL: https://issues.apache.org/jira/browse/WICKET-4357
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.4
>            Reporter: Michael Allan
>            Assignee: Peter Ertl
>            Priority: Minor
>              Labels: cache
>
> 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.

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