[
https://issues.apache.org/jira/browse/TRINIDAD-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-158.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.0.2-core
Assignee: Adam Winer
If you use ExternalContext.redirect(), this now works.
If you use ServletResponse.redirect() , and do so in a filter that is called
*after* the Trinidad filter, this will also work.
> PPR fails on session timeout with form-based authentication
> -----------------------------------------------------------
>
> Key: TRINIDAD-158
> URL: https://issues.apache.org/jira/browse/TRINIDAD-158
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.0.1-incubating-core-SNAPSHOT
> Environment: OC4J container 10.1.3
> Reporter: Cosma Colanicchia
> Assignee: Adam Winer
> Fix For: 1.0.2-core
>
>
> This problem is related to web applications with form-based container managed
> security.
> Suppose you have a view with a paged <af:table>, and that the session timed
> out. When you try to move on the next page (or to sort the table), the same
> page will be redrawn and no JSF processing will happen at all, because the
> container has forwarded the request to the login page. Due to the behaviour
> of PPR, the login page isn't shown to the user, that has no way to know
> what's happened. You can write a log line with a scriptlet in the login page
> to see that the forward has happened.
> Trying to set partialTriggers="false" in <afh:head>, <afh:body>, <af:form>
> and <af:table> doesn't help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
