[jira] Updated: (JS2-930) Expires header set to 0 does not cause round-trip in IE

["Dennis Dam (JIRA)" <je...@portals.apache.org>]

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

Dennis Dam updated JS2-930:
---------------------------

    Fix Version/s:     (was: 2.2.0)
                   2.2.1

they're using a workaround in html now by setting the meta-equiv  "Cache-Control" to "max-age=-1".

> Expires header set to 0 does not cause round-trip in IE
> -------------------------------------------------------
>
>                 Key: JS2-930
>                 URL: https://issues.apache.org/jira/browse/JS2-930
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Components Core
>            Reporter: Dennis Dam
>            Assignee: Dennis Dam
>            Priority: Minor
>             Fix For: 2.2.1
>
>
> As reported by Remco Nabuurs. Jetspeed sets the following HTTP response headers by default:
> Cache-Control: no-store, no-cache, private
> Pragma: no-cache
> Expires: 0
> To force a round trip in IE when pressing the BACK button, the expires header needs to be set to -1.  Firefox and Safari assign a higher priority to the expires header and perform a round trip. When an application makes use of Ajax calls in-between requests, and an application architecture is adhered (the Ajax calls change server state), this leads to pages with out-of-sync data.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org