javascript – Make Axios send cookies in its requests automatically-ThrowExceptions

Exception or error:

I am sending requests from the client to my Express.js server using Axios.

I set a cookie on the client and I want to read that cookie from all Axios requests without adding them manually to request by hand.

This is my clientside request example:

axios.get(`some api url`).then(response => ...

I tried to access headers or cookies by using these properties in my Express.js server:


Neither of them contained any cookies. I am using cookie parser middleware:


How do I make Axios send cookies in requests automatically?


I set cookie on the client like this:

import cookieClient from 'react-cookie'

let cookie = cookieClient.load('cookie-name')
if(cookie === undefined){
      axios.get('path/to/my/cookie/api').then(response => {
        if(response.status == 200){
'cookie-name',, {path:'/'})

While it’s also using Axios, it is not relevant to the question. I simply want to embed cookies into all my requests once a cookie is set.

How to solve:

I had the same problem and fixed it by using the withCredentials property.

XMLHttpRequest from a different domain cannot set cookie values for their own domain unless withCredentials is set to true before making the request.

axios.get('some api url', {withCredentials: true});


I am not familiar with Axios, but as far as I know in javascript and ajax there is an option

withCredentials: true

This will automatically send the cookie to the client-side. As an example, this scenario is also generated with passportjs, which sets a cookie on the server


It’s also important to set the necessary headers in the express response. These are those which worked for me:

app.use(function(req, res, next) {
  res.header('Access-Control-Allow-Origin', yourExactHostname);
  res.header('Access-Control-Allow-Credentials', true);
  res.header('Access-Control-Allow-Headers', 'Origin, X-Requested-With, Content-Type, Accept');



{ withCredentials: true } or axios.defaults.withCredentials = true

From the axios documentation

withCredentials: false, // default

withCredentials indicates whether or not cross-site Access-Control requests should be made using credentials

If you pass { withCredentials: true } with your request it should work.

A better way would be setting withCredentials as true in axios.defaults

axios.defaults.withCredentials = true


Another solution is to use this library:

which integrates “Tough Cookie” support in to Axios. Note that this approach still requires the withCredentials flag.


How do I make Axios send cookies in requests automatically?

set axios.defaults.withCredentials = true;

or for some specific request you can use axios.get(url,{withCredentials:true})

this will give CORS error if your ‘Access-Control-Allow-Origin’ is set to
Therefore make sure to specify the url of origin of your request

for ex: if your front-end which makes the request runs on localhost:3000 , then set the response header as

res.setHeader('Access-Control-Allow-Origin', 'http://localhost:3000');

also set



You are getting the two thinks mixed.

You have “react-cookie” and “axios”

react-cookie => is for handling the cookie on the client side

axios => is for sending ajax requests to the server

With that info, if you want the cookies from the client side to be communicated in the backend side as well, you will need to connect them together.

Note from “react-cookie” Readme:

Isomorphic cookies!

To be able to access user cookies while doing server-rendering, you
can use plugToRequest or setRawCookie.

link to readme

If this is what you need, great.

If not, please comment so I could elaborate more.


for people still not able to solve it, this answer helped me.
stackoverflow answer: 34558264

one needs to set {withCredentials: true} in both GET request as well the POST request (getting the cookie) for both axios as well as fetch.


So I had this exact same issue and lost about 6 hours of my life searching, I had the

withCredentials: true

But the browser still didn’t save the cookie until for some weird reason I had the idea to shuffle the configuration setting: + 'api/login', {
    }, {
        withCredentials: true,
        headers: {'Access-Control-Allow-Origin': '*', 'Content-Type': 'application/json'

Seems like you should always send the ‘withCredentials’ Key first.

Leave a Reply

Your email address will not be published. Required fields are marked *