As started here: https://github.com/angular/angular.js/issues/7771
Lucas Galsafó (@*lgalfaso) *says to apply the flag in config work-around. It's how I achieve the functionality, indeed. But this does not solve the problem: Traversing interceptors, check the config flag, and return immediately when the interceptor does not apply Consequence: As interceptors are in a promise chain, $q creates defers that are resolved, without any need. This can cause a performance downgrade with complex Apps Ajax-intensive with several interceptors. merging per-request interceptors with global interceptors is not complex, IMHO. global-request-interceptors -> per-request-request-int -> HTTP REQUEST -> per-request-response-int -> global-response-interceptors. WDYT? Regards, Javier -- 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.
