Add path

(only available for the HTTP based business application rules) This page describes how to define (a path) to which real web servers incoming requests are forwarded.

1. Enable path-specific routing and click Add new path.
2. Specify the path details.

   Path

   Enter the path for which you want to create the site path route.

   Example: /products/.

   Web server

   Select the web servers which are to be used for the specified path.

   Authentication

   Select the web app authentication profile. Select Create new to create a new authentication profile.

   You can also create an authentication profile from the Web server > Authentication policies page.

   Allowed client networks

   Select or add the allowed networks that should be able to connect to the hosted web server.

   Blocked client networks

   Select or add the denied networks that should be blocked to your hosted web server.

   Sticky session cookie

   Click the toggle switch to ensure that each session is bound to one web server. If enabled, a cookie is passed to the user’s browser, which causes Sophos XG Firewall to route all requests from this browser to the same real web server. If the server is not available, the cookie will be updated, and the session will switch to another web server.

   Hot-standby mode

   Click the toggle switch if you want to send all requests to the first selected web server, and use the other web servers only as a backup. The backup servers are only used in case the main server fails.

   As soon as the main server starts functioning, the sessions will switch back - unless you have selected the Sticky session cookie option.

3. Click Save.