Here's my solution for this https://github.com/Narzerus/angular-permission
El jueves, 7 de noviembre de 2013 09:59:27 UTC-3, Witold Szczerba escribió: > > Sander is right. > If you cannot fix the server side, so it throws 401's at logged in > users, but there is something else in response which can point you to > the truth, you can insert one more $http filter before and fix the > error status code, so the one designed to catch 401's won't get > invalid responses. > > Regards, > Witold Szczerba > > 2013/11/7 Sander Elias <[email protected] <javascript:>>: > > Hi OpenNota, > > > > That is a server issue! In this case the server should return an 403 in > > stead of a 401! Or perhaps another error code that better suits the > problem > > at hand. > > > > 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] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > Visit this group at http://groups.google.com/group/angular. > > For more options, visit https://groups.google.com/groups/opt_out. > -- 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.
