Why does Axios in the browser ignore my Cookie header?

Cookie is a forbidden request header in browsers. Use CookieMan to write the live jar, or run Axios in Node.

Should the output include the Cookie: prefix?

This serializer writes name=value; name=value only. Add the header name in Axios. Pasting a line that already starts with Cookie: is accepted on input.

How do I keep Set-Cookie from the Axios response?

In Node, read response.headers["set-cookie"], paste those lines here as Set-Cookie format, convert to JSON or Netscape. Browsers store Set-Cookie themselves.

Axios Cookie Header from JSON Export

Build an Axios Cookie header from JSON cookies

Axios in Node sends a Cookie header you attach yourself; convert a JSON export to that name=value; name=value line here. In a browser, Axios cannot force HttpOnly cookies — the header is ignored or forbidden.

This is the request header, not Set-Cookie. If you have response headers, use Cookie header vs Set-Cookie first.

Axios Cookie headerAxios cookiesJSON to Cookie headeraxios headers Cookie

1
Export JSON from Chrome
CookieMan JSON Array. Remove cookies you do not want on the API call.
2
Convert to Header String
Paste below. Copy the output. The serializer does not emit a Cookie: prefix — Axios wants the value only.
3
Attach in Node Axios
Set headers.Cookie on the instance or the request. Do not ship the header in frontend bundles.

Paste JSON cookie array

Output format

Output

Cookies are credentials. Conversion stays in this page — delete the file when you are done.

Node Axios snippet

            import axios from "axios";

const cookieHeader = "session_id=abc123; theme=dark"; // from this converter

const api = axios.create({
  baseURL: "https://api.example.com",
  headers: { Cookie: cookieHeader },
});

const { data } = await api.get("/v1/me");

Browsers block setting Cookie from JavaScript for your own origin’s HttpOnly cookies, and CORS plus forbidden headers stop you from attaching Cookie to cross-site XHR. This header path is for Node, curl, and other non-browser HTTP clients.

Header versus a real cookie jar

Approach	Keeps Domain / Secure / HttpOnly?	Where it works
`headers.Cookie` string	No — values only	Node Axios, httpie, fetch in Node
Netscape jar + curl	Domain, Secure, HttpOnly prefix	CLI
CookieMan Import JSON	Full attributes	Chrome / Edge

tough-cookie and axios-cookiejar-support exist if you need a jar in Node. This page stops at producing the header or a cookies.txt you can load elsewhere.

Related guides

July 22, 2026 3 min read

Postman Cookie Header to JSON

Paste a Postman Cookie header and turn name=value pairs into a JSON array. Domains default to localhost until you set them — then import or send via curl.

Postman cookiesPostman Cookie header Open the guide

August 7, 2026 3 min read

Cookie Header vs Set-Cookie Conversion

A Cookie request header is name=value pairs. Set-Cookie response lines carry Domain, Path, flags and Expires. Convert each separately — they are not interchangeable.

Cookie vs Set-CookieSet-Cookie to JSON Open the guide

July 30, 2026 3 min read

HTTPie Session Cookies from JSON

Convert a JSON cookie export into a Cookie header for httpie -A or a Netscape jar for curl-compatible sessions. Domains must be real hosts, not localhost.

HTTPie cookieshttpie session Open the guide