The issue is that when it returns the errors for all other cases, it does not return the full error (which includes config, response, etc.), but a simplified version that has basic info (message, error name, etc.).
Any idea what I am doing wrong in my interceptor that is preventing it from returning the full error response?
my code: https://gist.github.com/cryocaustik/49c9e39bee2a16b3fa69e78716ae5105
can anyone give me a hand?, i'm trying to post with axios, but nothing happens, here is my code
https://i.imgur.com/nWVAmi7.png
this is where i call the function
https://i.imgur.com/BwSCKRh.png
i'm in node.js
this is the console output
https://i.imgur.com/F6cLcqW.png
Hello there, recently I have updated to v0.19.0, but found that the relative query path behaviour is not the same as it was in v0.18.1.
I'm working in a Vue.js project, and using the default TypeScript setup provided by vue-cli.
In Jest, I've set up the testURL as 'http://localhost/test/', and in the test, I'm trying to query with axios.get('api/healthcheck') for example. The log shows that I'm querying the path http://localhostapi/healthcheck, instead of http://localhost/test/api/healthcheck. However 0.18.1 has the expected behaviour.
I've checked the Jest version I'm using, they are the same, there is no changes at Jest side.
I'd like to make a small but important contribution, the
axios.isTimeoutfunction.I've made a PR, but some tests are failing, probably easy to fix for long term mantainers.
Can anyone take a look?
axios/axios#2495
timeout of 0ms exceededon XHR it is reported in rollbar notifying that error is generated by axios 0.18.0. i have no idea why it is happening. This issue is already created axios/axios#2103 .- There is no timeout set , basically which means it is set to 0. (indefinite timeout)
- why it is giving an error
timeout of 0ms exceeded? - what can be done to handle this situation ?
Thank you.
axios.get(stringUrl, {responseType: 'stream'}).then( ... )const mystream = new Stream();
mystream.pipe = function(dest) {
dest.write(`
{"name": "xxx", "id": 1}
{"name": "yyy", "id": 2}
`);
return dest;
};mock.onGet(stringUrl, {responseType: 'stream'}).reply(200, mystream); UnhandledPromiseRejectionWarning: Unhandled promise rejection.nock
nock(someStringUrl).get(somePath).reply(200, () => {
return fs.createReadStream(path.join(__dirname, 'fixtures/data.json'))
})
hey there: was wondering about the axios custom instance creation. I was wondering what I'm doing wrong -> I create an instance and export it -> then after some time I call an api to authenticate and after authentication I wan't to write the token to the axios instance with:
api.defaults.headers.common['Authorization' ] = '${user.token_type} ${user.access_token}';But sadly after I call the API with a get request to get some data the "Authorization" is missing in the request.
Any ideas? Help?
Cheers!
hey there: was wondering about the axios custom instance creation. I was wondering what I'm doing wrong -> I create an instance and export it -> then after some time I call an api to authenticate and after authentication I wan't to write the token to the axios instance with:
api.defaults.headers.common['Authorization' ] = '${user.token_type} ${user.access_token}';But sadly after I call the API with a get request to get some data the "Authorization" is missing in the request.
Any ideas? Help?
Cheers!
used the interceptors :D
intercepters hook. how can I make sure the refresh_token API in the code bellow call once if I have 2 or more API requests call at the same time?thanks for supporting <3
httpClient.interceptors.response.use(
response => response,
error => {
const isTokenRefreshing = 'isTokenRefreshing';
const { response: { status, data: { key } }, config } = error;
const isValidRefreshToken = !localStorage.getItem(isTokenRefreshing) &&
status === UNAUTHORIZED_CODE &&
key === REFRESH_KEY
console.log("isTokenRefreshing", localStorage.getItem(isTokenRefreshing))
console.log("status: ", status, " key: ", key)
if (isValidRefreshToken) {
localStorage.setItem(isTokenRefreshing, true);
return httpClient.post('fresh_token').then(() => {
localStorage.removeItem(isTokenRefreshing)
return httpClient(config);
}).catch( error => {
localStorage.removeItem(isTokenRefreshing)
localStorage.removeItem('login');
window.location.replace('/login');
return Promise.resolve(error);
});
}
// while(localStorage.getItem(isTokenRefreshing)) {
// console.log('refreshing')
// }
if(status === UNAUTHORIZED_CODE && key === REFRESH_KEY){
localStorage.removeItem(isTokenRefreshing)
return httpClient(config);
}
return Promise.reject(error);
}
);
set-cookie response properly from the server and it's only an http cookie.
withCredentials: true