Technical Tip: How to configure an additional port for the URL when the application is already on-boarded with HTTPS port 443 or another port

Description

This article describes how to configure FortiAppSec application settings when the application URL has a different port to answer, and the main page is onboarded with HTTPS port 443 or any other port.

Scope

FortiAppSec Cloud.

Solution

An administrator onboarded an application named 'test.com' with a frontend port 443 and an origin server configured in such a way that some of the URL's response on a different port, not on HTTPS port 443.

When the user requests the URL https://test.com/folder and the URL /folder responds on HTTPS port 8443, since the application frontend is already onboarded with HTTPS port 443, there is no way to add another port in this case.

Solution:

The administrator can configure a content routing policy where admins can bind the URL to an origin server with HTTPS port 8443, so that when the traffic requests the URL from the users, FortiAppSec will know that it must use HTTPS port 443 to get the response from the origin server for the /folder URL.

Note:

By default, the application is not enabled with a content routing module. The admin must enable it from the Add module -> Content routing: