Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1.5
    • Fix Version/s: None
    • Labels:
      None

      Description

      Doing this inside the generate closure produces the correct caching behavior, otherwise its possible for the browser to get content from cache without even checking the etag / lastModified date:

      response.setHeader 'Cache-Control', 'no-cache'
      response.setHeader 'Pragma', 'no-cache'

        Activity

        Hide
        Marc Palmer added a comment -

        I'm not clear that this is a bug. The generate closure is supposed to call the appropriate "cache" method for its requirements.

        Show
        Marc Palmer added a comment - I'm not clear that this is a bug. The generate closure is supposed to call the appropriate "cache" method for its requirements.
        Hide
        Luis Arias added a comment -

        Hi Marc, this definitely looks old. I can say that I'm not using the above "workaround" at all now, so it's probably a fluke. Probably a bad test case on my end.

        Show
        Luis Arias added a comment - Hi Marc, this definitely looks old. I can say that I'm not using the above "workaround" at all now, so it's probably a fluke. Probably a bad test case on my end.

          People

          • Assignee:
            Marc Palmer
            Reporter:
            Luis Arias
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: