> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/origin-sni-request.md).
# Origin SNI Request
Configure the Server Name Indication (SNI) value used when the CDN establishes an HTTPS connection to your origin server.
**Origin SNI Request** specifies the domain sent in the SNI extension during the TLS handshake between the CDN and the origin. The origin server uses this value to select the appropriate TLS certificate and virtual host.
You can manage Origin SNI Request in the [Medianova Control Panel](https://cloud.medianova.com) or via the [Origin Settings API](https://clients.medianova.com/api-documentation/performance-cdn/origin-settings#put-api-v1-cdn-organization_uuid-resource-resource_uuid-3).
{% hint style="info" %}
**Origin Settings** is available for CDN Resources that use **My origin** as the content source. The section is not displayed when **Object storage** is selected.
{% endhint %}
### Configure Origin SNI Request
Configure a resource-level SNI value for HTTPS connections from the CDN to your origin.
{% stepper %}
{% step %}
### Open Origin Settings
Open your CDN Resource and select **Origin Settings**.
{% endstep %}
{% step %}
### Enable Origin SNI Request
Enable **Origin SNI Request**.
The domain field becomes available.
{% endstep %}
{% step %}
### Enter the SNI Domain
Enter the domain that the CDN should send as the SNI value when establishing an HTTPS connection to the origin.
The domain should correspond to the TLS certificate and virtual host configuration on the origin server.
{% hint style="info" %}
If an SNI value is configured for an individual origin in [**Advanced Origin Settings**](/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/advanced-origin-settings.md), that origin-specific value is used for requests routed to that origin.
{% endhint %}
{% endstep %}
{% step %}
### Save the Configuration
Select **Save** in the pending changes bar.
Review the pending changes and confirm the update to apply the configuration to the CDN Resource.
{% endstep %}
{% endstepper %}
## How Origin SNI Request Works
When the CDN establishes a TLS connection to an HTTPS origin, it can include the configured domain in the SNI extension of the TLS handshake.
The origin server can use the SNI value to select the appropriate TLS certificate and virtual host when multiple domains are served from the same endpoint.
Origin SNI Request affects the **CDN-to-origin connection**. It does not change the hostname requested by the end user.
## Origin-Specific SNI
Advanced Origin Settings also provide an **Origin SNI request** field when configuring a custom origin.
This allows an SNI value to be defined for an individual origin used by a URI match rule. When an origin-specific SNI value is configured, it takes precedence over the resource-level Origin SNI Request value for that origin.
{% hint style="info" %}
For more information, see [Advanced Origin Settings](/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/advanced-origin-settings.md).
{% endhint %}
## When to Configure Origin SNI Request
Configure Origin SNI Request when the HTTPS origin requires a specific server name during the TLS handshake, such as when multiple domains or virtual hosts share the same origin endpoint.
Ensure that the configured SNI domain corresponds to the certificate and virtual host expected by the origin server.
## Troubleshooting
If the CDN cannot establish the expected HTTPS connection to the origin:
* Verify that **Origin SNI Request** is enabled.
* Verify that the configured SNI domain is correct.
* Confirm that the origin is configured to serve the expected TLS certificate for the SNI domain.
* Check whether an origin-specific SNI value is configured in [**Advanced Origin Settings**](/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/advanced-origin-settings.md).
## Related Concepts
* [Advanced Origin Settings](/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/advanced-origin-settings.md)
* [Origin Settings API](https://clients.medianova.com/api-documentation/performance-cdn/origin-settings)
---
# 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://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/origin-settings/origin-sni-request.md?ask=&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.
