Uploaded image for project: '[Read Only] - Hippo Site Toolkit 2'
  1. [Read Only] - Hippo Site Toolkit 2
  2. HSTTWO-3869

Parsing of expires headers fails if expires is set directly on backing HttpServletResponse

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • None
    • 4.1.1
    • None
    • None
    • Platform Sprint 144

    Description

      In HSTTWO-3554 I made a fix to correctly parse the expires header because it was assumed to always be in RFC1123 date format. However this is only the case when the setDateHeader is invoked on a HstResponse. If setDateHeader is invoked directly on the backing HttpServletResponse, you get the long (ms since epoch) back (the container will later translate it to RFC1123)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              aschrijvers Ard Schrijvers
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: