> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/custom-error-page.md).

# Custom Error Page

Redirect users to custom pages when specific edge-generated HTTP error responses occur.

Redirect users to a custom URL when specific edge-generated HTTP error responses occur.

**Error Page** allows you to define custom redirect behavior for edge-generated `4xx` and `5xx` responses. Each configuration maps an HTTP status code to an Error Page URL and specifies whether the redirect is permanent or temporary.

{% hint style="info" %}
Error Page applies to error responses generated by the CDN edge. Error responses returned directly by your origin are not affected.
{% endhint %}

Error Page is configured per CDN Resource in the [Medianova Control Panel](https://cloud.medianova.com) under **Page Rules**.

## Configure Error Page

{% stepper %}
{% step %}

### Enable Error Page

Open your CDN Resource and select **Page Rules**.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FLkT1Uw73LtMdqNmPuFer%2Fimage.png?alt=media&amp;token=742f3b9e-7fc5-4b83-a7c6-3a510620d385" alt=""><figcaption></figcaption></figure>

Enable **Enable Error Page**.
{% endstep %}

{% step %}

### Create an Error Page

Select **Create Error Page**.

<figure><img src="https://542970813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtK7oIwmhUHdEJcaH4Hx8%2Fuploads%2FU5bq0dyd3hEPJPJo6l9l%2Fimage.png?alt=media&amp;token=d2c71cfd-307c-42e6-ae87-d63b6b3eaa9f" alt=""><figcaption></figcaption></figure>

The **Create Error Page** panel opens.
{% endstep %}

{% step %}

### Configure the HTTP Status Code

Enter the **HTTP Status Code** that should trigger the redirect.

Set the configuration to **Active** or **Inactive**.
{% endstep %}

{% step %}

### Enter the Error Page URL

Enter the destination in **Error Page URL**.

For example:

```
https://example.com/errors/404.html
```

The browser is redirected to this URL when the CDN generates the configured error response.
{% endstep %}

{% step %}

### Select the Redirect Type

Select the redirect returned to the browser:

* **301 Permanent** — Indicates that the redirect is permanent.
* **302 Temporary** — Indicates that the redirect is temporary.

{% hint style="warning" %}
Use **302 Temporary** unless the error page is intended to be permanent. Browsers and search engines may cache a `301` redirect for an extended period. If content is later published at the affected URL, users may continue to be redirected to the error page.
{% endhint %}
{% endstep %}

{% step %}

### Create the Error Page

Select **Create** to add the Error Page configuration.
{% endstep %}
{% endstepper %}

## Configuration Options

<table><thead><tr><th width="200.4000244140625">Option</th><th>Description</th></tr></thead><tbody><tr><td><strong>HTTP Status Code</strong></td><td>Defines the edge-generated HTTP error response that triggers the redirect.</td></tr><tr><td><strong>Active / Inactive</strong></td><td>Determines whether the Error Page configuration is applied.</td></tr><tr><td><strong>Error Page URL</strong></td><td>Defines the URL to which the browser is redirected.</td></tr><tr><td><strong>301 Permanent</strong></td><td>Returns a permanent redirect to the configured Error Page URL.</td></tr><tr><td><strong>302 Temporary</strong></td><td>Returns a temporary redirect to the configured Error Page URL.</td></tr></tbody></table>

## How Error Page Works

When an active Error Page configuration matches an edge-generated error response:

1. The CDN generates the configured `4xx` or `5xx` response.
2. The Error Page configuration matches the HTTP status code.
3. The CDN returns the configured `301` or `302` redirect.
4. The browser follows the redirect to the configured Error Page URL.

Multiple Error Page configurations can be created to handle different HTTP status codes.

## Important Notes

* Error Page applies to edge-generated `4xx` and `5xx` responses.
* Origin-generated error responses are not affected.
* Use **302 Temporary** when the redirect should not be cached as a permanent redirect.
* Ensure that the configured Error Page URL remains accessible.
* Avoid configurations that could redirect the Error Page URL back to itself.

## Related Concepts

* [HTTP Response Codes](/getting-started/concepts/http-response-codes.md)
* [Page Rules](/products/performance-cdn/static-content-delivery/advanced-configuration/page-rules.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/static-content-delivery/advanced-configuration/custom-error-page.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.