Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Handbook

Configuring error pages

When backend real servers are unavailable or another status code for other module (ex: WAF/DoS/Auth), FortiADC can respond to clients attempting HTTP/HTTPS connections with a customized HTML error page. Once you create an HTML error page, you can select it in virtual server configurations.

The current error page file package only requests index.html to replace 503 error message when there’s no servers in pool, we also extend the support to these files listed below:

File Name

MUST

Guidelines

Index.html

Yes

This page will replace 503 error message page.

200.html

No

This page will replace 200 error message page.

202.html

No

This page will replace 202 error message page.

205.html

No

This page will replace 205 error message page.

400.html

No

This page will replace 400 error message page.

401.html

No

This page will replace 401 error message page.

403.html

No

This page will replace 403 error message page.

404.html

No

This page will replace 404 error message page.

405.html

No

This page will replace 405 error message page.

406.html

No

This page will replace 406 error message page.

408.html

No

This page will replace 408 error message page.

410.html

No

This page will replace 410 error message page.

413.html

No

This page will replace 413 error message page.

500.html

No

This page will replace 500 error message page.

501.html

No

This page will replace 501 error message page.

502.html

No

This page will replace 502 error message page.

504.html

No

This page will replace 504 error message page.

default.html

No

This page will replace all other error page doesn’t include in the package(excluding 503)

You do not have to create an HTML error page if you want to simply send a basic text error message when backend servers are unavailable. Instead, you can enter an error message in a text box from within the virtual server configuration. See Error Message.

Before you begin:

  • You must have Read-Write permission for Server Load Balance settings.
  • Copy the error message file to a location you can reach from your browser; the error page file must be named index.html and contained in a tar, tar.gz, or zip file. The maximum file size is 1 MB.
To upload an error message file:
  1. Go to Server Load Balance > Application Resources.
  2. Click the Error Page tab.
  3. Click Create New to display the configuration editor.
  4. Enter the name of the error page. You will use this name to select the error page in virtual server configurations. No spaces.
  5. Click Choose File and browse and select the error message tar, tar.gz, or zip file. The maximum file size is 1MB.
  6. Enter the Virtual Path of the error page. This virtual path will conflict with the custom authentication form base page's virtual path and also with SAML's server URL configuration and Captcha path.
  7. Save the configuration.

It is possible to modify error pages that you have already created. To do so, double-click the error page or select the (edit) icon in the row of the error page that you want to modify, and upload a new error message tar, tar.gz, or zip file as above.

Note: While it is possible to modify the error message file, once an error page is created, you cannot modify its name.

Configuring error pages

When backend real servers are unavailable or another status code for other module (ex: WAF/DoS/Auth), FortiADC can respond to clients attempting HTTP/HTTPS connections with a customized HTML error page. Once you create an HTML error page, you can select it in virtual server configurations.

The current error page file package only requests index.html to replace 503 error message when there’s no servers in pool, we also extend the support to these files listed below:

File Name

MUST

Guidelines

Index.html

Yes

This page will replace 503 error message page.

200.html

No

This page will replace 200 error message page.

202.html

No

This page will replace 202 error message page.

205.html

No

This page will replace 205 error message page.

400.html

No

This page will replace 400 error message page.

401.html

No

This page will replace 401 error message page.

403.html

No

This page will replace 403 error message page.

404.html

No

This page will replace 404 error message page.

405.html

No

This page will replace 405 error message page.

406.html

No

This page will replace 406 error message page.

408.html

No

This page will replace 408 error message page.

410.html

No

This page will replace 410 error message page.

413.html

No

This page will replace 413 error message page.

500.html

No

This page will replace 500 error message page.

501.html

No

This page will replace 501 error message page.

502.html

No

This page will replace 502 error message page.

504.html

No

This page will replace 504 error message page.

default.html

No

This page will replace all other error page doesn’t include in the package(excluding 503)

You do not have to create an HTML error page if you want to simply send a basic text error message when backend servers are unavailable. Instead, you can enter an error message in a text box from within the virtual server configuration. See Error Message.

Before you begin:

  • You must have Read-Write permission for Server Load Balance settings.
  • Copy the error message file to a location you can reach from your browser; the error page file must be named index.html and contained in a tar, tar.gz, or zip file. The maximum file size is 1 MB.
To upload an error message file:
  1. Go to Server Load Balance > Application Resources.
  2. Click the Error Page tab.
  3. Click Create New to display the configuration editor.
  4. Enter the name of the error page. You will use this name to select the error page in virtual server configurations. No spaces.
  5. Click Choose File and browse and select the error message tar, tar.gz, or zip file. The maximum file size is 1MB.
  6. Enter the Virtual Path of the error page. This virtual path will conflict with the custom authentication form base page's virtual path and also with SAML's server URL configuration and Captcha path.
  7. Save the configuration.

It is possible to modify error pages that you have already created. To do so, double-click the error page or select the (edit) icon in the row of the error page that you want to modify, and upload a new error message tar, tar.gz, or zip file as above.

Note: While it is possible to modify the error message file, once an error page is created, you cannot modify its name.