You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2010/09/27 17:32:33 UTC

[jira] Resolved: (WICKET-3081) AJAX call to timed-out session should result in failureScript rather than redirect to SessionExpiredPage

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

Igor Vaynberg resolved WICKET-3081.
-----------------------------------

      Assignee: Igor Vaynberg
    Resolution: Won't Fix

currently, in 1.4.x+ you will get a page expired error page. there is no point in invoking a failure script because the page will still be missing. page expired error page is the only valid response.

> AJAX call to timed-out session should result in failureScript rather than redirect to SessionExpiredPage
> --------------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-3081
>                 URL: https://issues.apache.org/jira/browse/WICKET-3081
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>         Environment: Wicket 1.3.7
>            Reporter: Peter Parson
>            Assignee: Igor Vaynberg
>
> Currently, it does not seem to be possible to react in a user-friendly manner if an AJAX request detects that its session has timed out.
> I suggest that a valid AJAX response should be returned, invoking the failureScript (if there is one, otherwise SessionExpiredPage is a valid response)

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