You can customize the following FortiWeb HTML pages:
Pages that FortiWeb presents to clients when it authenticates users.
FortiWeb uses these pages when the client authentication method in a site publishing configuration is HTML Form Authentication. For details, see Single sign-on (SSO) (site publishing).
- The error page FortiWeb uses to respond to a HTTP request that violates a policy and the configured action is Alert & Deny or Period Block.
- The error page FortiWeb uses to respond to a AJAX request that violates a policy and the configured action is Alert & Deny or Period Block.
- The "Server Unavailable!" page that FortiWeb returns to the client when none of the server pool members are available either because their status is Disable or Maintenance or they have failed the configured health check.
FortiWeb uses each page for specific server policy.
Follow steps below to configure an error or authentication page:
- Go to System > Config > Replacement Message.
- Select Replacement Message.
- Select the message you want to edit in the list of messages or click Create New to create a new message.
You can also select the predefined one to take it as a template, or select a message and click Clone to clone this message.
- You can enable Replacement Message for AJAX requests to respond to a AJAX request, and configure the AJAX block page message. You must enable it by going to System > Config > Feature Visibility first.
- If you have selected Attack block page and want to change the HTTP response code it displays, click Edit HTTP Response Code. Enter a new value for the code, and then click Apply. For details, see Attack block page HTTP response codes.
- In the bottom-right pane, edit the HTML code as required.
The results of any changes you make are displayed immediately in the bottom-left pane.
- Click Save to save your changes or Restore Defaults to revert to the preset version of the page.
- Select the replacement message when you edit a policy.
For details about using macros in the code, see Macros in custom error and authentication pages.
Go to System > Config > Replacement Message, and select Disclaimer tab. You can edit the disclaimer message. Click Save to save your changes or click Restore Defaults to revert to the preset version.
You can specify the HTTP response code that the attack block message page displays. If the error status code allows an attacker to fingerprint a vulnerable application, you can customize it to display a more vague reply. (For all other pages, you cannot change the default response code.)
The following codes are examples of HTTP response codes:
200—OK. Typically indicates success, and accompanies resource requested by the client.
400—Bad Request. Typically indicates wrong syntax.
403—Forbidden. Typically indicates inaccessible files.
404—File Not Found. Typically indicates missing files.
500—Internal Server Error. Typically indicates one of many possible conditions such as a servlet runtime error.
501—Not Implemented. Typically indicates a non-existent function on the web application.
When it generates error and authentication messages, FortiWeb generates some of the message content using macros. It uses two type of macros: label macros and image macros.
Although you can add the predefined macros to your custom messages, you cannot create macros and you cannot modify the label macros. You can modify an image macro to reference a predefined image or one that you have uploaded.
You can use the following label macros anywhere in the HTML code for Attack Block Page and Server Unavailable Message messages:
Inserts one of the following URLs:
|%%SOURCE_IP%%||The source IP address of the client that attempted to access the web service.|
|%%DEST_IP%%||The IP address of the web server.|
|%%VSERVER_IP%%||The IP address of the virtual server.|
|%%EVENT_ID%%||An ID number that identifies the attack type. Use this number to help you locate the log for the event in the FortiWeb attack log.|
You can use the following label macros anywhere in the HTML code for the Site Publish Authentication messages:
|%%ORG_LOCATION_VAL%%||The original URL that the client tried to access.|
|%%LOGIN_POST_URL%%||The login URL where users post their credentials.|
|%%TOKEN_POST_URL%%||The login URL where users insert their token code.|
|%%RSA_LOGIN_POST_URL%%||The login URL where users post their RSA SecurID credentials.|
|%%RSAC_POST_URL%%||The login URL where users post their RSA SecurID credentials.|
|%%ACCOUNT%%||The username credential of a user who exceeded the maximum number of login attempts.|
|%%PERIOD_TIME%%||The length of time that FortiWeb prevents a user from attempting to log in again, after the user has exceeded the allowed number of login attempts. The site publishing policy specifies the value.|
The message ID number idenfities the attack log message ID, and can be used to map the event to the log in the FortiWeb attack log.
Use the following format to add an image macro anywhere in a custom error or authentication message:
<image_name> is the name of either a predefined image or one you have uploaded. To view or upload images, go to System > Config > Replacement Message, and then select Manage Images tab. For details, see Adding images in error or authentication pages.
For example, in the default Attack Block Page message, the macro
%%IMAGE%%:logo_v2_fnet%% adds the predefined image
logo_v2_fnet. If you add the image
test to the list of images, use
%%IMAGE%%:test%% to add it to the HTML code.
- Go to System > Config > Replacement Message.
- Click Manage Images tab, and then click Create New.
- Specify a name for the image file, select its content type, and then click Choose File to browse to the file and select it.
Ensure the image is no larger than 24 kb and that its type matches the value you have selected for Content Type.
- Click OK, and then click Return to return to the list of customizable pages.
By default, the Login Page replacement message is formatted to simply display any reply message it receives from the authentication server.
For example, locate the following section of the replacement message:
<h2> %%REPLY_TAG%% </h2>
Replace the macro and its formatting with the following script: