Customizing error and authentication pages (replacement messages)

You can customize the following FortiWeb HTML pages:

FortiWeb uses these pages for all server policies. If you require a page content that is customized for a specific policy, create an ADOM that contains the custom pages for that policy.

Attack block page HTTP response codes

You can specify the HTTP reponse 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:

Macros in custom error and authentication pages

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.

Label macros

You can use the following label macros anywhere in the HTML code for Attack Block Page and Server Unavailable Message messages:

Macro Description
%%URL%%

Inserts one of the following URLs:

  • The URL of a web page blocked by either the web filtering or URL blocking feature.
  • The URL of a web page that contains a blocked file that a client has tried to download.
%%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:

Macro Description
%%ORG_LOCATION_VAL%% The original URL that the client tried to access.
%%REPLY_TAG%% The authentication server reply message. For an example of how you can customize the message by replacing this macro with JavaScript, see Customize the message returned for LDAP errors (%%REPLY_TAG%% macro).
%%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.

 

 

Image macros

Use the following format to add an image macro anywhere in a custom error or authentication message:

%%IMAGE:<image_name>%%

where <image_name> is the name of either a predefined image or one you have uploaded. To view or upload images, go to System > Status > Replacement Message, and then click Manage Images. For more information, see To view or add images used 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.

To customize an error or authentication page

1.  If your custom page requires a custom image, see To view or add images used in error or authentication pages.

2.  Go to System > Config > Replacement Message.

3.  Select the page you want to edit in the list of pages.

4.  If you 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.

5.  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.

For information about using macros in the code, see Macros in custom error and authentication pages.

6.  Click Save to save your changes or Restore Defaults to revert to the preset version of the page.

To view or add images used in error or authentication pages

1.  Go to System > Config > Replacement Message.

2.  Click Manage Images, and then click Create New.

3.  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 selected for Content Type.

4.  Click OK, and then click Return to return to the list of customizable pages.

Customize the message returned for LDAP errors (%%REPLY_TAG%% macro)

By default, the Login Page replacement message is formatted to simply display any reply message it receives from the authentication server.

However, you can use JavaScript to customize the message that is displayed.

For example, locate the following section of the replacement message:

<h2>
            %%REPLY_TAG%%
</h2>

Replace the macro and its formatting with the following script:

<h2>
<script type="text/javascript">
              var r = "%%REPLY_TAG%%"
                  if (r == "Failed to search user DN" )
                  {
                    document.write("<b>Invalid Username</b>")
                      }
              else if (r == "Failed to bind LDAP server" )
              {
                document.write("<b>Invalid Password</b>")
                  }
              else if (r == "Username or password can't be null" )
              {
                document.write("<b>Username or password empty</b>")
                  }
              else if (r == "Invalid credentials" )
              {
                document.write("<b>Invalid Username or Password</b>")
                  }
              else if (r != "" )
              {
                document.write(r)
                  }
              
            </script>
</h2>