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 (JIRA)" <ji...@apache.org> on 2011/09/14 14:39:09 UTC

[jira] [Resolved] (WICKET-4051) max-age header is set in milliseconds rather than seconds

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

Peter Ertl resolved WICKET-4051.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.1

> max-age header is set in milliseconds rather than seconds
> ---------------------------------------------------------
>
>                 Key: WICKET-4051
>                 URL: https://issues.apache.org/jira/browse/WICKET-4051
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.0
>            Reporter: Emond Papegaaij
>            Assignee: Peter Ertl
>             Fix For: 1.5.1
>
>         Attachments: headerfix.diff
>
>
> According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html the max-age in Cache-Control should be set in seconds, but WebResponse.enableCaching sets it in milliseconds. The attached patch fixes this.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira