> For the complete documentation index, see [llms.txt](https://ploegert.gitbook.io/til/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ploegert.gitbook.io/til/general/networking/allow-cross-origin-requests-to-include-cookies.md).

# Allow Cross-Origin Requests To Include Cookies

## Allow Cross-Origin Requests To Include Cookies

When making a cross-origin fetch request from a client (e.g. browser) to a server, all kinds of CORS protections are enforced by the browser. One of those protections, by default, is to avoid XSS attacks by not sending credentials (e.g. cookies, authorization headers or TLS client certificates) in the request or expose credentials to the client JavaScript code.

This is controlled by the [Access-Control-Allow-Credentials](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Credentials) header.

If we want to include things like cookies in the request, then we need to have both the client-originating request and the server to agree to allow credentials.

The client-side fetch will need to specify that credentials should be included:

```javascript
fetch(url, {
  credentials: 'include'
})
```

The server, either in response to a GET or a preflight request, will need to do two things. First, the response headers need to have `Access-Control-Allow-Credentials` set to `true`. Second, the [`Access-Control-Allow-Origin`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin) will need to name the specific origin (the client). In other words, the allowed origin cannot be set to `*`.

[source](https://stackoverflow.com/a/24689738/535590)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ploegert.gitbook.io/til/general/networking/allow-cross-origin-requests-to-include-cookies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.