Hi Ssaniel,
I agree that one would expect that browsers would handle this on their own. The do if you navigate to such an URL, so why not on 302 one would say?. I can imagine situation where you don't want that if you are creating your own app, so that might be the whole reason. But 302's are not that common. you don't see them often, and I think that is the reason those are overlooked in almost any framework. So, indeed, you have to handle it on your own. Luckily for you, you chose angular. You can create an interceptor <https://docs.angularjs.org/api/ng/service/$http>that encapsulates the handling of 302's. Hope this helps you a bit. 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/d/optout.
