Hi Sander! Only the proxy knows whether the user is still logged in or not. So as soon as he tries to do a REST call out of the application, and for some reason he is not logged in anymore (maybe he logged out in another browser tab), the proxy would return a 302 redirect... This is where i'm stuck :-(
Michael Am Mittwoch, 29. Januar 2014 12:57:37 UTC+1 schrieb Sander Elias: > > Hi Michael, > > You can't handle status 302 with javascript! Even angularJS can change > anything about that. > However, I guess there is a moment in your app that sends off the user to > the authentication server? Before sending them of, store the current user > status in localStorage. When the redirect comes back, and your page gets > reloaded, you can pick up this status out of localStorage, and set the user > on her/his merry way! > > Regards > Sander > > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
