diff --git a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-origins/origins.mdx b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-origins/origins.mdx
index ff0895fbf5..f8e8b1b378 100644
--- a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-origins/origins.mdx
+++ b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-origins/origins.mdx
@@ -34,7 +34,7 @@ In this guide, there are separate instructions for API v3 and API v4. If you're
1. [Access Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Connectors**.
-2. Click the **+ + Connector** button.
+2. Click the **+ Connector** button.
3. In the **General** section, give your connector a unique and descriptive name (`My Object Storage Connector`).
4. In the **Connector Type** section, select **HTTP**.
@@ -55,7 +55,7 @@ To activate the Connector in your application:
1. Access the **Rules Engine** tab.
2. Edit the default rule or add a new request rule.
-3. Give a name for your rule.
+3. Give your rule a name.
4. Select **Request Phase**.
5. Under the **Criteria** section, select the variable `${uri}`.
6. As a comparison operator, select **is equal**.
@@ -63,27 +63,27 @@ To activate the Connector in your application:
8. In the **Behaviors** section, select **Set Connector** from the behavior list.
9. Select the new Connector you created.
10. Click the **Save** button.
-11. Wait a few minutes for the changes to propagate and access `xxxxxxxxxx.map.azionedge.net/httpbin`.
+11. Wait a few minutes for the changes to propagate, then access `xxxxxxxxxx.map.azionedge.net/httpbin`.
-When you [create an application](/en/documentation/products/start-with-a-template/), a default origin is created and activated automatically. This guide will show you how to create and activate a new origin with different configurations without removing or editing the default origin.
+When you [create an application](/en/documentation/products/start-with-a-template/), a default origin is created and activated automatically. This guide shows you how to create and activate a new origin with different configurations without removing or editing the default origin.
1. Access [Azion Console](/en/documentation/products/guides/how-to-access-azion-console/) > **Applications**.
2. Click the application for which you want to configure a new origin.
3. Select the **Origins** tab.
4. Click the **+ Origin** button.
-5. Give your new origin a name. For example: `httpbin.org`
-6. Under **Type**, keep the option **Single Origin** selected.
+5. Give your new origin a name. For example: `httpbin.org`.
+6. Under **Type**, keep **Single Origin** selected.
:::tip
To implement load balancing algorithm for multiple origins, see the [guide on multiple origins with Load Balancer](/en/documentation/products/guides/build/multiple-origins/).
:::
7. Under **Protocol Policy**, select **Enforce HTTPS**.
-8. Under **Address**, add `httpbin.org`
+8. Under **Address**, add `httpbin.org`.
9. Under **Host Header**, add `customhost.com`.
:::tip[Choosing the right Host Header value]
@@ -95,36 +95,36 @@ The **Host Header** controls which value Azion sends in the `Host` HTTP header w
**Important**: if your origin enforces Host-based access controls, IP allowlists tied to a specific hostname, or CDN configurations that validate the `Host` header, changing this value may cause the origin to reject requests. Verify your origin's virtualhost configuration before modifying this field.
:::
-10. Leave **Path** blank.
-11. Click the **Save** button.
+10. Leave **Origin Path** blank.
+11. Click **Save**.
:::note
If your origin is under a host followed by a path, such as `https://bucket.s3.amazonaws.com/applications/your-app`, you must separate the URL and add the host `bucket.s3.amazonaws.com` into the **Address** field and add the path `/applications/your-app` into the **Origin path** field.
:::
-You've created a new origin, but it isn't active in your application yet. You need to define what will trigger a request to the new origin.
+The origin is created, but it isn't active yet. You need to create a Rules Engine rule to route requests to it.
1. Navigate to the **Rules Engine** tab.
2. Click the **+ Rule** button.
-3. Give a name for your rule.
+3. Give your rule a name.
4. Select **Request Phase**.
5. Under the **Criteria** section, select the variable `${uri}`.
:::note
-The `${uri}` variable may already be selected by default if you didn't activate **Application Accelerator**. For more information on Applications modules, see the [Applications documentation](/en/documentation/products/build/applications/#modules).
+The `${uri}` variable may already be selected by default if you haven't activated **Application Accelerator**. For more information on application modules, see the [Applications documentation](/en/documentation/products/build/applications/#modules).
:::
6. As a comparison operator, select **is equal**.
7. As an argument, add `/httpbin`.
8. In the **Behaviors** section, select **Set Origin** from the behavior list.
9. Select the new origin you created.
-10. Click the **Save** button.
-11. Wait a few minutes for the changes to propagate and access `xxxxxxxxxx.map.azionedge.net/httpbin`.
+10. Click **Save**.
+11. Wait a few minutes for the changes to propagate, then access `xxxxxxxxxx.map.azionedge.net/httpbin`.
-1. Run the following `POST` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/):
+1. Run the following `POST` request in your terminal. Replace `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/) and `` with [your application ID](/en/documentation/products/guides/build/configure-main-settings/):
/origins' \
@@ -294,11 +294,11 @@ curl --location 'https://api.azionapi.net/edge_applications//ori
| Key | Description |
| --- | --- |
- | `name` | Sets the string in value as a name of the origin. |
- | `origin_type` | Sets the new origin type to `single_origin`. For more information on load balancing, check [Work with multiple origins](/en/documentation/products/guides/build/multiple-origins/). |
- | `addresses` | Takes a list of objects for each address of the origin. Since this is an entry of the single origin type, you may only send one object with the `address` value in the array. |
- | `origin_protocol_policy` | When `https`, enforces an HTTPS connection with the origin, not affecting the protocol from user requests. |
- | `host_header` | Sets the value of the `Host` header sent to the origin. Use a specific FQDN (e.g., `customhost.com`) when your origin serves a single virtualhost. Use `${host}` to forward the `Host` header received from the user's request, which is useful when your origin serves multiple virtualhosts. If your origin enforces Host-based access controls, ensure this value matches what the origin expects. |
+ | `name` | Name of the origin. |
+ | `origin_type` | Origin type. Set to `single_origin` for a single address. For load balancing across multiple addresses, see [Work with multiple origins](/en/documentation/products/guides/build/multiple-origins/). |
+ | `addresses` | List of origin address objects. For `single_origin`, you can only send one object in the array. |
+ | `origin_protocol_policy` | Connection protocol between edge nodes and the origin. When set to `https`, enforces HTTPS regardless of the protocol used by the end user. |
+ | `host_header` | Value sent in the `Host` header to the origin. Use a specific FQDN (e.g., `customhost.com`) for a single virtualhost. Use `${host}` to forward the end user's `Host` header, useful when your origin serves multiple virtualhosts. |
2. You'll receive a response similar to this:
@@ -331,11 +331,11 @@ curl --location 'https://api.azionapi.net/edge_applications//ori
}
`} />
-:::caution[warning]
-Endpoints that require origin identification use the `origin_key` value. For example, a `PATCH` request for an origin must be made to the URL `https://api.azionapi.net/edge_applications//origins/`. This doesn't apply to cases when you must reference an origin outside the `/origins/` endpoints, such as when creating a new rule to activate your origin.
+:::caution
+Endpoints that require origin identification use the `origin_key` value, not the `origin_id`. For example, a `PATCH` request must target `https://api.azionapi.net/edge_applications//origins/`. The exception is when referencing an origin outside the `/origins/` endpoints — such as when creating a Rules Engine rule — where `origin_id` is used instead.
:::
-3. Run the following `POST` request in your terminal, replacing `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/), the `` variable with [your application ID](/en/documentation/products/guides/build/configure-main-settings/), and the `` variable with the origin ID from when you [created a new origin via API](#via-api):
+3. Run the following `POST` request in your terminal. Replace `[TOKEN VALUE]` with your [personal token](/en/documentation/products/guides/personal-tokens/), `` with [your application ID](/en/documentation/products/guides/build/configure-main-settings/), and `` with the origin ID returned in the previous step:
/rules_engine/request/rules' \
@@ -363,12 +363,31 @@ curl --location 'https://api.azionapi.net/edge_applications//rul
}'
`} />
-4. You'll receive a response confirming that the rule was created.
-5. Wait a few minutes for the changes to propagate and access `xxxxxxxxxx.map.azionedge.net/httpbin`. Also, try accessing any other unconfigured URI: you should receive a `404` error.
+4. A successful response confirms the rule was created.
+5. Wait a few minutes for the changes to propagate, then access `xxxxxxxxxx.map.azionedge.net/httpbin`. Try accessing any other unconfigured URI — you should receive a `404` error.
:::tip
Check the [Azion API documentation](https://api.azion.com/) to know more about all features available via API.
:::
-
\ No newline at end of file
+
+
+
+:::note[Host Header behavior]
+The **Host Header** field controls which value Azion sends in the `Host` header when forwarding requests to your origin.
+
+- **`${host}`**: passes the `Host` header received from the end user directly to the origin. Use this when your origin serves multiple virtualhosts from the same address and needs to distinguish between them.
+- **A specific domain name** (for example, `customhost.com`): sends a fixed value regardless of what the user requested. Use this when your origin responds to a virtualhost at an address different from the one configured in DNS, or when you need to enforce a specific hostname for origin-side routing, SSL certificate matching, or access control.
+
+Leaving the field blank causes Azion to use the value set in the **Address** field as the default Host header.
+:::
+
+:::caution[Origin configuration restrictions]
+Keep the following constraints in mind when configuring an origin:
+
+- The **Address** field must be a valid FQDN or IPv4/IPv6 address. Do not include the protocol (`http://` or `https://`) in this field; use the **Origin Protocol Policy** setting instead.
+- If your origin content lives under a subpath (for example, `bucket.s3.amazonaws.com/apps/my-app`), place the hostname in **Address** and the path in **Origin Path**. Combining both in the **Address** field will cause request failures.
+- Changing the origin address or Host Header of an active origin affects all rules that reference it. Review your Rules Engine configuration before making changes in production.
+- For origins that require HMAC authentication (such as private object storage buckets), you must provide valid **Region**, **Access Key**, and **Secret Key** credentials. Incorrect or missing credentials will result in `403` errors from the origin.
+:::
\ No newline at end of file