Hello, i had the same issue, what i did is add a specific header to every request coming from the CAS Server and add an interceptor in ajax calls. If the status is 200 and the header is present it means the ajax call has been redirected.
it works in my case, maybe there is a better solution. J-Emmanuel Le 13/01/2016 23:34, Jonathan Labin a écrit : > I have used java-cas-client to configure my web application to > authenticate via a CAS server. > I have noticed that after a timeout or when Single Log-out is > activated in a different application, a user initiating an ajax call > on the still-open application results in some issues. > > It looks like the ajax call is being redirected to the CAS login page > and returning a "success" status to the browser. This results in > unexpected behavior by my application as the ajax call response > handlers have not been configured to detect the html of the login page > as a response. > > Is there a recommended way of configuring either the CAS server to > send an error code or something to trigger the browser to redirect the > loaded page or for configuring the application for recognizing this > case and reloading the home page of the application? > > Thanks. > -- > You received this message because you are subscribed to the Google > Groups "CAS Community" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > Visit this group at > https://groups.google.com/a/apereo.org/group/cas-user/. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
