Hi Ssaniel, I just checked for you, but I was wrong this morning. (coffee did set yet :) ) Most browsers do handle the 302 on their own. However, it happens that in most case you get an 302 redirect to login, witch then gives a 40x (2 mostly) that the user is not authenticated. So, you can tell your server guy, that they are sending back the wrong response. if auth is needed, they should send back an 402, not an 302. (or you can work around it, often an easier solution.)
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.
