Details
Description
The BlockingServlet doesn't specify cache-controls on the response header, as
the PersistentFacesServlet does. When using synchronousMode, and redirects to
achieve basic back button functionality, Firefox caches the page and doesn't
repost the page, so the viewID on the server doesn't change. Any subsequent
navigation will result in unintended consequence.
repro steps:
1. go to page A
2. go to page B
3. back button to page A
4. click commandLink on page A to page B
5. expected behaviour:
page B is displayed
actual behaviour:
page A is redisplayed
A workaround using a PhaseListener to set the cache-control on the
BlockingServlet response header resolves this behaviour.
the PersistentFacesServlet does. When using synchronousMode, and redirects to
achieve basic back button functionality, Firefox caches the page and doesn't
repost the page, so the viewID on the server doesn't change. Any subsequent
navigation will result in unintended consequence.
repro steps:
1. go to page A
2. go to page B
3. back button to page A
4. click commandLink on page A to page B
5. expected behaviour:
page B is displayed
actual behaviour:
page A is redisplayed
A workaround using a PhaseListener to set the cache-control on the
BlockingServlet response header resolves this behaviour.
Re-assigning to Mircea for comment and approach to including in 1.6.