Hi all! We're having a similar issue with http status code 302. We're building an AngularJS App. Authentication is done by a third party proxy who will return http status 302 and redirect to login when the user is not logged in... Unfortunately we cannot change this behaviour as other applications behind the proxy rely on this redirect. Do you have any idea how we could solve this?
As far as I understand there's no way I can handle status 302 in an AngularJS application ( https://groups.google.com/forum/#!topic/angular/GKkdipdMbdo), am I right? A solution offered by the proxy development team was, that they could offer a special servlet that will tell us wether we're logged in or not (and return e.g. status 401). So we would have to make this servlet call before EVERY other rest call from our AngularJS application... What do you think about this? Cheers Michael Am Sonntag, 3. Juli 2011 11:56:35 UTC+2 schrieb Vojta Jína: > > Yes, browser doesn't allow you to handle 302 on your own. > You can use different 2xx status code for redirect and do the redirect by > your JS code... > V. > -- 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.
