Don't send default header

[kyeotic]

If a header has been set as a default, there does not appear to be any way to skip it on an individual request. Setting null or undefined doesn't do anything.

[rubennorte]

Could you provide some code example that shows that behaviour? What default header are you trying to unset?

[kyeotic]

If I set axios.defaults.headers.common['Content-Type'] = 'application/json', I cannot unset that that header for an individual request, I can only set it to another value.

[rubennorte]

How did you tried to unset the header? Using something like this?

axios.request('/path', {
  headers: {
    'Content-Type': null
  }
});

[kyeotic]

Yes. That did not work

[rubennorte]

Sorry I missed the method in my example. Could have been that what made it not work?

[kyeotic]

I have tried setting the method as well. I suspect it has to do with an Object.assign() somewhere just not paying attention to the undefined value.

[mzabriskie]

@tyrsius what version of axios are you using? I just wrote a test to try and reproduce this and it passed. I'm wondering if this may have been fixed in a newer version.

For reference here is my test:

it('should remove default headers when config indicates', function (done) {
  var instance = axios.create();
  instance.defaults.headers.common['Content-Type'] = 'application/json';

  instance.post('/foo/bar/', {
    firstName: 'foo',
    lastName: 'bar'
  }, {
    headers: {
      'Content-Type': null
    }
  });

  getAjaxRequest().then(function (request) {
    testHeaderValue(request.requestHeaders, 'Content-Type', null);
    done();
  });
});

[Madalosso]

I had this problem too.
I'm trying to remove the header 'Authorization' from 'common' but the only way that I've found to make it work is delete the property from the axios.defaults.header, make the request, and then add the property back again.
This will be easier when this bug is fixed

[chipit24]

This is also a problem for me (using axios v0.14.0), especially for endpoints that use Access-Control-Allow-Headers, in which case I need to make sure certain headers aren't sent with the request at all.

[SepiaGroup]

i am using version 15.2 and when i do

headers: {
      'Content-Type': null
    }

it does set the header value to null. but i really need the header name to be removed completely.

for example when using s3 and generating a presigned url to post a file to a bucket you can not have an Authenticate header. but i have a default Authorization set because the vast majority of my requests require it for my own api.

the way i got around this is by doing the following

    var instance = axios.create();
    instance.defaults.headers.common = {};

    instance.put(signedUrl, file, {headers: {'Content-Type': file.type}})
        .then(function (result) {
            console.log(result);
        })
        .catch(function (err) {
            console.log(err);
        });

Edit: this does not work as expected. the issue is that when you clear the headers

instance.defaults.headers.common = {};

it removes it at a global level. this will log me out as i use a header for Auth.

to get around this issue until there is a better way of handling global config i am passing the required headers on every call, not ideal.

[paseo]

#545

[axelgenus]

I had the same problem but solved with

delete axios.defaults.headers.common["Authorization"]; // or which ever header you have to remove

[Christilut]

I have the exact situation as @SepiaGroup
I tried to overwrite it with null and '' but then AWS sees null as my Authorization and complains.
I tried to delete it from the instance but then my Authorization is deleted globally so I get 403 on my own server.

I guess my workaround will be to use an old XHR for this but it makes me sad :(

[yaronlevi]

+1 Also stuck with not being able to clear the default header for a specific call.

[lukasborawski]

+1

[ojczeo]

+1

[tannerlinsley]

I'm also seeing this behavior in the latest version (0.16.2). Sadness ensues :(

[lzp4ever]

just delete it

delete instance.defaults.headers.common.Authorization

the way below is not working.

I think we could create a logout method that recreate the axios instance to replace the old one.

let instance = axios.create({options})

function: logout () {
    instance = axios.create({options})
}

[wdews]

@lzp4ever that would work in most instances, I expect. But in cases where someone has added request and response interceptors, or done more configuration of the instance beyond simply passing in config options, wouldn't your approach require that all of that be redone?

Just wondering if perhaps @axelgenus's solution is cleaner and requires less "resetting" of an entire Axios instance from which you're attempting to remove a particular customized header from.

[maryokhin]

Would be nice to be able to NOT send the default header without deleting properties :)

[aaronfahey]

+1

[Jenan]

+1

[oodgaard]

+1. It does seem sad that you cannot remove the headers for an instance. This means that all instances have a reference to the global variable.

[dkanas]

+1

[Spacelapp]

+1

[shyamchandranmec]

+1 Please fix this issue.

[michaelcpuckett]

+1

[matthewlilley]

+1

[mikhoq]

I am running into rather similar situation but with a GET request:

1. GET http://www.saasserviceprovider.com/notpublicapi with header of Authorization: Bearer mytoken
2. Redirects to AWS S3 endpoint. Redirect URL has a query string: X-Amz-Signature=blahblahblah appended.
3. AWS S3 rejects call because two Authenication:

• Header: Authorization bearer token
• Query string: X-Amz-Signature=blahblahblah

Neither transformRequest, transformResponse, axios.interceptors.request, axios.interceptors.response appears to be able to allow me to inject myself into the process and temporarily remove the Authorization Header when hitting the redirection to AWS S3 - presumably if I could get in after a redirect I could do something to effect of delete headers.Authorization.

Same call with request api/postman/etc works.

Seriously though... has to be better way (within axios)

@iyerusad Did you find any better way than your workaround? I'm facing the same issue, and it's frustrating that I don't seem to be able to intercept the redirect and delete the Authorization header just for that follow-up / redirect request (to amazon in this case) 🤔

[iyerusad]

@iyerusad Did you find any better way than your workaround? I'm facing the same issue, and it's frustrating that I don't seem to be able to intercept the redirect and delete the Authorization header just for that follow-up / redirect request (to amazon in this case) 🤔

Not really - using option B. from below.

The options I evaluated:
A. Adopt alternative wrapper/client (e.g. fetch api? request? request seemed to work but is apparently deprecated). This might be cleanest option but means switching to another http client syntax.

B. Wrap my workaround into a function and use that function for requests that I know run into this issue - ugly seemingly less efficient but using this at the moment.

C. Hope I am an idiot and using axios wrong and there is saner workaround with axios.

D. Axios get fix/patch?

[chinesedfan]

@mikhoq @iyerusad Would you mind to open a new issue to track your problem? Because it is different with the current one, which may have been fixed in #2844.

[iyerusad]

No problem - Opened #2855.

@mikhoq please add comment there if you have public repro endpoint.

[guanzo]

So apparently transformRequest gets called for GET requests? I tried this and it worked, it only deleted the header for the current request.

transformRequest: [(data, headers) => {
    delete headers.common.Authorization
    return data
}]

But the docs say

// transformRequest allows changes to the request data before it is sent to the server
// This is only applicable for request methods 'PUT', 'POST', 'PATCH' and 'DELETE'

Which made me think transformRequest wouldn't be called for GET requests, but it is. So what does this line actually mean?

"This is only applicable for request methods 'PUT', 'POST', 'PATCH' and 'DELETE'"

Perhaps, "This is potentially only useful for ...." ....? It's misleading imo.

[idjemaoune]

this works:
headers: {
'content-type': 'application/json',
'Authorization': null,
}

[Roms1383]

Tried setting { headers: { 'Content-Type' = null } } without success,
so to add to @axelgenus helpful comment, I had to go a bit further :

import Axios from 'axios'
const client = Axios.create({
  // ...
  transformRequest: [(data, headers) => {
    // add required "Content-Type" whenever body is defined
    if (data) headers['Content-Type'] = 'application/x-www-form-urlencoded'
    return data
  }],
})
// completely remove "Content-Type" from instance by default
delete client.defaults.headers.common['Content-Type']
delete client.defaults.headers.post['Content-Type']
delete client.defaults.headers.put['Content-Type']
delete client.defaults.headers.patch['Content-Type']
// ...

Use case was implementing requests layer for Bitstamp API V2 authentication method.

[JerbyIchrak]

I have an OPTION request before my PUT request, so @aaronatmycujoo 's transformRequest solution worked for my OPTION request, but the Authorization header was still applied to my PUT request.

Ultimately i ended up making separate instances for auth vs public requests so my auth header was only applied to the auth instance.

// do not configure auth header
export const publicAxios = axios.create(...)

// configure auth header
export const authAxios = axios.create(...)

// no auth header present for public instance
publicAxios.put(...)

I tried this solution ,it seems right but didn't work for me because i need to add some custom interceptors , so i made a seperate file containing another instance i called it publicInstance and i used it for all my public routes . It works !

[yulafezmesi]

Sperate your auth interceptor and use it whenever necessary.

if (getAuthToken()) {
  httpClient.interceptors.request.use(authInterceptor);
} else {
  httpClient.interceptors.request.eject(authInterceptor);
}

[EKOLX]

I tried every single suggestion from each post but none of them help.
Axios still sending 'Content-Type' whenever I try to delete it.
From React Native app I'm trying to upload file into AWS S3 via presigned url, and with Content-Type I get 403 error.
I tried it with postman and without any headers, it uploads successfully, but I don't understand why I can't exclude Content-Type from http request.

[Pixelatex]

@EKOLX is correct... just been through this whole circus myself. Why the bleeping hell is it so hard to remove a default header.

I need to work with some major company's api who refuse to accept a request that doesn't have exactly the params that they specify.. in this case that you can't send a content-type header...

[jasonsaayman]

@Pixelatex please can you open a new issue and then tag me in it? Then I can have a look.

[SaimumIslam]

just keep the header in axios it works like charm.
{```

  "Content-Type": "",

}

[kameshdhana]

I had the same problem but solved with

delete axios.defaults.headers.common["Authorization"]; // or which ever header you have to remove

The problem is if I remove it the endpoint call fails

[Rickyv92]

Having this issue, using "axios ^0.18.0"

This companies application injects an 'x-api-key' using interceptors.

I've tried using the methods posted above, but the only ones that remove the x-api-key remove them globally and breaks the entire app.

Any updates or help would be very helpful.

Thanks

[iyerusad]

Having this issue, using "axios ^0.18.0"

Using "axios": "^0.21.1", issue appears to be resolved.

In any case current is 1.4.0, should update as 0.18 is pre-1.0 and ~5 years old.

[Rickyv92]

In any case current is 1.4.0, should update as 0.18 is pre-1.0 and ~5 years old.

Good point, i'll look into upgrading