> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/security/cors-configuration.md).

# CORS Configuration

**Introduction to CORS (Cross-Origin Resource Sharing)**

CORS, or Cross-Origin Resource Sharing, is a fundamental web security mechanism, it defines the rules for when and how a web page hosted on one domain can make requests to access resources, such as data or services, on another domain. CORS is a crucial aspect of web security, as it helps prevent malicious websites from making unauthorized requests to sensitive data.

**Understanding Allowed CORS hosts**

In Limio the Allowed CORS hosts list serves as a whitelist, permitting specific domains to make cross-origin requests to the Limio API and access its resources.

The list allows "headless" access to APIs. This means that services or scripts running on servers or in environments without a traditional web browser (i.e., headless) can still make secure requests to the Limio API.

Go to General Settings > Site Security:

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-756efa707ce379bddb5ce715a830f9633d50fc50%2Fimage%20(222).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/product/settings/security/cors-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
