Wicket
  1. Wicket
  2. WICKET-4051

max-age header is set in milliseconds rather than seconds

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.0
    • Fix Version/s: 1.5.1
    • Component/s: wicket
    • Labels:
      None

      Description

      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.

      1. headerfix.diff
        0.7 kB
        Emond Papegaaij

        Activity

        Emond Papegaaij created issue -
        Emond Papegaaij made changes -
        Field Original Value New Value
        Attachment headerfix.diff [ 12494397 ]
        Peter Ertl made changes -
        Assignee Peter Ertl [ pete ]
        Hide
        Peter Ertl added a comment -

        thanks a lot for reporting ... fixed in trunk!

        Show
        Peter Ertl added a comment - thanks a lot for reporting ... fixed in trunk!
        Peter Ertl made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 1.5.1 [ 12315430 ]
        Resolution Fixed [ 1 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        4h 35m 1 Peter Ertl 14/Sep/11 13:38

          People

          • Assignee:
            Peter Ertl
            Reporter:
            Emond Papegaaij
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development