--- name: azion-deploy-the-applications-proxy-template description: >- Deploy an application in front of your origin that bypasses the cache and forwards cookies on one URL route, with the Applications Proxy template. --- # Deploy the Applications Proxy template You can deploy the Applications Proxy template from Azion Console to bypass the cache on one URL route of your origin. The template places an [application](/en/documentation/platform/applications/) in front of the origin. It creates one rule in [Rules Engine for Applications](/en/documentation/platform/applications/rules-engine/), and the rule stays editable after the deployment. The rule's criterion compares the `${uri}` variable with the route you enter, such as `/url_route`, through the `starts_with` operator. A request that matches runs three behaviors: - [Set Connector](/en/documentation/platform/applications/rules-engine/#set-connector) sends the request to `Default Origin`, the origin the template creates from the address you enter. - [Bypass Cache](/en/documentation/platform/applications/rules-engine/#bypass-cache) keeps Azion from caching the origin's response, so the application's cache settings do not apply to the route. - [Forward Cookies](/en/documentation/platform/applications/rules-engine/#forward-cookies) sends the origin's `Set-Cookie` header to the user. Bypass Cache acts on Azion's cache and not on the Tiered Cache layer. If a cache setting of the application turns on Tiered Cache, that layer still caches objects on the route for its minimum TTL. For more information, refer to [Tiered Cache](/en/documentation/platform/applications/cache/tiered-cache/). ## Prerequisites - The address of your origin, the server the application fetches the original content from. - Access to Azion Console. To sign in, refer to [Access Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/). --- ## Deploy the template The Applications Proxy template deploys from a form in Azion Console, and the form marks each mandatory field with an asterisk. The application it creates uses [Application Accelerator](/en/documentation/platform/applications/how-it-works/#application-accelerator) and [Functions](/en/documentation/platform/functions/), which can generate usage-related costs. For the rates, refer to [Pricing](/en/documentation/fundamentals/pricing/). Open the template's form in Azion Console: [Deploy](https://console.azion.com/create/azion/edge-application-proxy) To deploy the template from the form: 1. **Name the application** Enter a unique name for the application on Azion. A name already in use returns an error message. 2. **Enter the origin address** Enter the address of the origin the application fetches the original content from, such as `www.yourwebsite.com`. 3. **(Optional) Enter a custom host header** If your origin needs host information in the request header to return content, enter it, such as `${host}`. For more information on the host header, refer to [Origins](/en/documentation/platform/connectors/origins/). 4. **Enter the route to bypass** Enter the URL route the bypass rule applies to, such as `/url_route`. 5. **Start the deployment** Submit the form. A window shows the deployment logs while the deployment runs. When the deployment finishes, the page shows the application's information and the options to continue. The configuration takes a few minutes to propagate across Azion's distributed infrastructure. Until then, the link to the application can fail to show the page, so wait a few minutes and open it again. This video walks through the deployment of the Applications Proxy template: [How to deploy the Applications Proxy template](https://www.youtube.com/watch?v=BRoJ9lRZ80I) Deploy the Applications Proxy template, which bypasses the cache on one URL route of your origin. --- ## Open the bypass rule The rule the Applications Proxy template creates stays editable in the **Rules Engine** tab of the application. There you can change its route or its behaviors. To open the rule: 1. **Open the Applications page** Access [Azion Console](https://console.azion.com/) > **Applications**. The page lists every application in the account in alphabetical order. 2. **Search for the application** Enter the name you gave the application. The search filters the list by application name only. 3. **Select the application** 4. **Select the Rules Engine tab** 5. **Select the rule the template created** The rule opens for editing, with the criterion and the three behaviors the template set. For every field of the criterion and the behaviors, refer to [Rules Engine for Applications](/en/documentation/platform/applications/rules-engine/#bypass-cache). For the settings of the application itself, refer to [Main Settings](/en/documentation/platform/applications/main-settings/). To build an application by hand, with a connector and a rule of your own, refer to [Applications quickstart](/en/documentation/platform/applications/quickstart/). --- ## Next steps - [Rules Engine for Applications](/en/documentation/platform/applications/rules-engine.md#bypass-cache): Every option of Bypass Cache, Forward Cookies, and Set Connector, and the variables a criterion can test. - [Cache variation](/en/documentation/platform/applications/application-accelerator/cache-variation.md#bypass-cache-and-a-ttl-of-0): How Bypass Cache differs from a cache TTL of 0 on the same route. - [Configure cache policies for an application](/en/documentation/guides/application-performance/cache-and-purge/cache-settings.md): Set how Azion caches the content on the routes the bypass rule does not match. - [Applications best practices](/en/documentation/platform/applications/best-practices.md#rule-out-tiered-cache-before-you-rely-on-bypass-cache): Rule out Tiered Cache before you rely on Bypass Cache for a route.