--- name: azion-set-the-host-header-and-path-prefix-for-an-origin description: >- Choose the Host header a connector sends and the path it prepends, so the origin serves the right site and directory. --- # Set the Host header and path prefix for an origin You can set the `Host` header a [connector](/en/documentation/platform/connectors/) sends to its origin, and a path it prepends to every request, from Azion Console, the Azion CLI, or the API. Both settings apply to a connector of type `http`. The examples use `httpbin.org` as the origin, because it answers with the request it received, so each setting shows in its response. Replace it with the host name of your origin. --- Select the interface you use. The prerequisites and every task on this page follow that choice. ## Prerequisites - A connector of type `http`, and a workload whose application points a rule at the connector with the `Set Connector` behavior. To create both, refer to [Connectors quickstart](/en/documentation/platform/connectors/quickstart/). - The workload domain, or a domain of your own, that the workload answers on. **Console** - Access to [Azion Console](https://console.azion.com/). **CLI** - The [Azion CLI](/en/documentation/devtools/cli/), installed and authorized. - The ID of your connector. **API** - A [personal token](/en/documentation/fundamentals/personal-tokens/) and `curl`. - The ID of your connector. --- ## Send the origin's own host name By default, `host` is `${host}`, which sends the host the client requested. Keep the default for an origin that serves several virtual hosts and reads each request under its public name. Set a literal value when the origin answers only under its own name. The connector then sends that name for every request. **Console** To set the host name in Azion Console: 1. **Open the connector** Access [Azion Console](https://console.azion.com/) > **Connectors**, then select your connector. 2. **Enter the host name** In **Host**, enter `httpbin.org`. 3. **Select Save** Azion Console shows `Connector has been updated`. The Console refuses a value that is not a host name, an IP address, or a variable, with `Host must be a valid hostname, IP address, or variable.` **CLI** The CLI updates a connector from a file that carries the whole connector: its `name`, `type`, `attributes.addresses`, and the connection options you set. A file with `connection_options` alone fails with `Failed to decode the given 'json' file`. Copy your connector's current values into the file, then change `host`. To set the host name with the Azion CLI, save the connector as `connector.json`: ```json { "name": "my-connector", "type": "http", "attributes": { "addresses": [{"address": "httpbin.org"}], "connection_options": {"transport_policy": "force_https", "host": "httpbin.org"} } } ``` Then update the connector from the file. Replace `` with the ID of your connector: ```bash azion update connector --connector-id --type http --file connector.json ``` ```text Updated Connector with ID ``` The connector now sends `Host: httpbin.org` to the origin. **API** To set the host name with the API, send a `PATCH` request with only the key you change. A `PATCH` merges it into the stored connector: ```bash curl --request PATCH \ --url https://api.azion.com/v4/workspace/connectors/ \ --header 'Accept: application/json' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{"attributes":{"connection_options":{"host":"httpbin.org"}}}' ``` The API answers `202` with `"state": "pending"` and the full connector. `connection_options.host` reads `httpbin.org`, and the other connection options keep their values. An empty `host` is refused with `400` and `10018` `This field may not be blank.` To send the client's host again, set the value back to `${host}`. --- ## Prepend a path The path goes in front of the path the client requested, so the origin serves content from one of its directories. With `/anything`, a request for `/get` reaches the origin as `/anything/get`. With `/secure`, a request for `https:///index.html` reaches the origin as `/secure/index.html`. The prefix never appears in the client's URL. The value starts with `/`, and the default is no prefix. For a bucket of Object Storage, a connector of type `storage` carries its own `prefix` instead. For more information, refer to [Connector settings](/en/documentation/platform/connectors/settings/#storage). **Console** To set the path in Azion Console: 1. **Open the connector** Access [Azion Console](https://console.azion.com/) > **Connectors**, then select your connector. 2. **Enter the path** In **Path**, enter `/anything`. 3. **Select Save** Azion Console shows `Connector has been updated`. A path without the leading slash is refused with `Path must start with a forward slash (/)`. **CLI** To set the path with the Azion CLI, add `path_prefix` to the whole connector in `connector.json`: ```json { "name": "my-connector", "type": "http", "attributes": { "addresses": [{"address": "httpbin.org"}], "connection_options": {"transport_policy": "force_https", "host": "httpbin.org", "path_prefix": "/anything"} } } ``` Then update the connector from the file: ```bash azion update connector --connector-id --type http --file connector.json ``` ```text Updated Connector with ID ``` To read the connection options back: ```bash azion describe connector --connector-id --format json ``` The output carries the new path and the host name from the file: ```text "connection_options": { "dns_resolution": "both", "following_redirect": false, "host": "httpbin.org", "http_version_policy": "http1_1", "path_prefix": "/anything", "real_ip_header": "X-Real-IP", "real_port_header": "X-Real-PORT", "transport_policy": "force_https" }, ``` `path_prefix` carries `/anything`, and `host` carries the name from the file. **API** To set the path with the API, send a `PATCH` request with `path_prefix` alone: ```bash curl --request PATCH \ --url https://api.azion.com/v4/workspace/connectors/ \ --header 'Accept: application/json' \ --header 'Authorization: Token [TOKEN VALUE]' \ --header 'Content-Type: application/json' \ --data '{"attributes":{"connection_options":{"path_prefix":"/anything"}}}' ``` The API answers `202` with `"state": "pending"` and the full connector, where `connection_options.path_prefix` reads `/anything`. A value without the leading slash, such as `anything`, is refused with `400` and `28009` `Invalid path format. Must be a valid path.` --- ## Verify what the origin receives A connector change needs no new deployment. It reaches traffic over several minutes, and each data center applies it at its own moment. For more information, refer to [How Connectors works](/en/documentation/platform/connectors/how-it-works/#propagation). To see the request the origin received, send a request through your workload. Replace `` with the workload domain or your own domain: ```bash curl -s -D - https:///get ``` `httpbin.org` answers with the request it received, as JSON. Two fields show the connector's settings: `headers.Host` is the `Host` header, and `url` carries the path the origin received. With `host` at `${host}` and the path prefix `/anything`, the response reads: ```text HTTP/2 200 … server: gunicorn/19.9.0 … "headers": { … "Host": "", … }, … "url": "https:///anything/get" } ``` `url` carries `/anything/get`, so the connector prepends the path prefix. `headers.Host` carries the workload domain, the host the client requested. With `host` at `httpbin.org`, `headers.Host` reads `httpbin.org` instead. Send the request several times: an answer with the previous values comes from a data center that has not applied the change yet. --- ## Next steps - [Connector settings](/en/documentation/platform/connectors/settings.md#connection-options): Every connection option, its API field, its default, and its limits. - [How Connectors works](/en/documentation/platform/connectors/how-it-works.md#host-header): How the Host header, the path prefix, and the protocol shape the request the origin receives. - [Sign origin requests with HMAC](/en/documentation/guides/application-development/getting-started/sign-origin-requests-with-hmac.md): Serve a private bucket of an S3-compatible origin, with the bucket name as the path. - [Troubleshoot Connectors](/en/documentation/platform/connectors/troubleshooting.md): Fix a connector whose origin refuses requests or answers with an error.