Modify request headers before httpBuffer.retryAll() about angular-http-auth HOT 2 CLOSED

The solution is to use the $http.post, $http.get, $http.put, $http.patch, $http.delete, shortcuts instead of $http({ method: "POST"}).

This way they use the common headers which you can update at anytime,

from angular-http-auth.

What, if anything, needs to happen such that buffered $http requests are retried with either the up-to-date default configuration, or with an override that is specific to the retries?

Right now it looks like the config is bundled in the retry buffer... would it be correct/useful to take what's in the retry buffer, merge the new $http defaults onto it, and then merge anything provided by the loginConfirmed function as an extra level of controlling those requests?

So, the default behavior would be:

• take the buffered $http config for any request and apply the new (newly) current default $http config on top of that
• using the buffered configs as the basis for the ultimately applicable config when these retries occur only impacts the bufferred requests... everything else proceeds with $http defaults, whatever they may be when subsequent requests are made
• if, during the course of confirming the login, any changes should be applied to the bufferred requests, and such changes should not impact the longer-term behavior of $http, then the client specifies a config object when confirning the login to the service, such that it will override the config that would otherwise be used.

I think I should have written code to express that...

Basically, make sure that by default http-auth takes the combination of the fresh default $http config when it retries.

And for bonus points, let someone specify additional overrides to the defaults for purposes of only the retries.

from angular-http-auth.