| Description | This article provides a workaround for a custom Error Page for a Virtual Server with Content Routing. |
| Scope | FortiADC and FortiADC-VM. |
| Solution |
When using Content Routing for Virtual Server, the FortiADC does not reply with the custom Error Page but with the default Error Page for the 503 HTTP response status code when the client HTTP request does not match any Content Routing rule for the respective Virtual Server.
Step 1: Create a custom Error Page with a custom 503 page at Server Load Balance -> Application Resources -> Error Page.
Step 2: Create a Real Server Pool with no members (empty) at Server Load Balance -> Real Server Pool -> Real Server Pool.
Step 3: Create a new Content Routing (for example, 'empty_cr') at Server Load Balance -> Virtual Server -> Content Routing, select the Real Server Pool created in Step 2, and configure its matching condition to match the Virtual Path of the custom Error Page created in Step 1 (for example, /adc-page/).
Step 4: Add the Content Routing to the respective Virtual Server.
Step 5: Verify the custom Error Page by reproducing the 503 HTTP response status:
Related documents: |
