Order of applying request interceptors is reversed.

I’ve encountered a bug(or a feature) that my request interceptors were applied in reversed order.

This is the culprit: https://github.com/mzabriskie/axios/blob/2fe95621b0e4839f489210452ffc6d2cb0f90343/lib/core/Axios.js#L48

If you unshift interceptors one by one, then the last defined interceptor becomes the first in the chain.

Example:

axios.interceptors.request.use(config => {
  console.log('First');
  return config;
});
axios.interceptors.request.use(config => {
  console.log('Second');
  return config;
});

When we perform a request this is what we see in the console:

> Second
> First

If it’s intentional, I think it should be documented.

[rubennorte]

As this isn’t documented nor tested isn’t actually a bug, but I understand it should be executed in the proper order.

The tests for response interceptors test the actual order but those for the request don’t.

Are you willing to create a PR to solve this?

[le0nik]

Sure. PR: https://github.com/mzabriskie/axios/pull/1041