Axios request fail to authenticate while using headers

Describe the issue Upgrading from 0.18 to 0.19 version is causing an issue in HTTP requests - GET, POST when sending headers like cookie.

Example Code

  const requestOptions = {
    baseURL: 'http://localhost:3000',
    url: `${endPoint}${ids}`,
    method: 'GET',
    responseType: 'json',
    timeout: 100000,
    headers: {
      VerificationToken: userToken,
      Cookie: cookie,
      'Content-Type': 'application/x-www-form-urlencoded',
    },
  };

  axios(requestOptions)
    .then((response) => {
      // Trigger in case, if it is not authenticated
      if (typeof response.data === 'string') {
       console.log('It is working here');
      }else {
       console.log('It should Work here');
      }
    })
    .catch((error) => {
    });

Expected behavior, if applicable Api should return expected result as it was giving in ver 0.18.0`

Environment:

• Axios Version [e.g. 0.19.0]
• OS: [e.g. OSX Mojave]
• Browser [e.g. Chrome [Electron] ]
• Electron Version [e.g. 4.0.4]

Additional context/Screenshots It is working flawless in ver 0.18.0, but not in ver 0.19.0 if we hit request (GET, POST) that requires headers.

[chinesedfan]

Closed due to stale. And feel free to open a new issue if someone met similar problem.

@feed4rz It should be related to #2567 and will be fixed in #2844.

[feed4rz]

I am having the same problem.

On version 0.18.1 I was able to pass array of cookies ['a=b', 'c=d', ...] to headers option:

axios.get('https://google.com', {
  headers: {
    cookie: ['a=b', 'c=d']
  }
})

And it produced a valid cookie string in headers:

GET / HTTP/1.1\r\nAccept: application/json, text/plain, */*\r\ncookie: a=b; c=d\r\nUser-Agent: axios/0.18.1\r\nHost: google.com\r\nConnection: close\r\n\r\n

But since version 0.19.0 things have changed:

GET / HTTP/1.1\r\nAccept: application/json, text/plain, */*\r\ncookie: [object Object]\r\nUser-Agent: axios/0.19.0\r\nHost: google.com\r\nConnection: close\r\n\r\n

Array of cookies is not getting formatted anymore. Is this a bug or a feature?