> 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

Custom Error Page allows you to redirect users to a custom URL when specific HTTP error codes are generated by the CDN edge. 

This feature is commonly used to display branded error pages, access restriction notices, or custom user guidance instead of the default CDN error response.

{% hint style="info" %}
Custom Error Page applies only to edge-generated error responses. Errors returned directly by your origin server are not affected.
{% endhint %}

## How It Works

When the CDN generates a configured HTTP error response, it returns a redirect to the specified Error Page URL instead of displaying the default error page.

Each rule consists of three parameters:

| Parameter            | Description                                               |
| -------------------- | --------------------------------------------------------- |
| Status Code          | The HTTP error code that triggers the redirect (400–599). |
| Error Page URL       | The destination URL users are redirected to.              |
| Redirect Status Code | The HTTP redirect status code returned to the browser.    |

Multiple rules can be configured for different HTTP status codes.

## Configure Custom Error Page

In the [Medianova Control Panel](https://cloud.medianova.com), navigate to the CDN Resource and open the **Page Rules** tab.

{% stepper %}
{% step %}

### **Enable Custom Error Page**

Enable the **Status** toggle to activate custom error page handling.

<figure><img src="/files/3g441acMZoGzXt2qjDQh" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### **Specify the Status Code**

Enter the HTTP error code that should trigger the redirect.

Supported values range from `400` to `599`.
{% endstep %}

{% step %}

### **Configure the Error Page URL**

Enter the URL users should be redirected to when the configured error occurs.

Example:

```
https://www.example.com/access-denied.html
```

{% endstep %}

{% step %}

### **Select the Redirect Status Code**

Choose the HTTP redirect code returned to the browser.

Common values include:

* 301 (Permanent Redirect)
* 302 (Temporary Redirect)
  {% endstep %}

{% step %}

### **Save the Configuration**

Click **Submit** to deploy the updated configuration.
{% endstep %}
{% endstepper %}

## Configuration

### Status Code

Defines the edge-generated HTTP status code that triggers the redirect.

Supported values range from `400` to `599`.

### Error Page URL

Defines the URL users are redirected to when the configured status code occurs.

The URL should be publicly accessible and return a valid response.

### Redirect Status Code

Defines the redirect response returned to the client.

Common values include:

| Code | Description        |
| ---- | ------------------ |
| 301  | Permanent redirect |
| 302  | Temporary redirect |

For additional details about redirect responses, see the HTTP Response Codes documentation.

### Example

The following configuration:

* Status Code: `403`
* Error Page URL: `https://www.example.com/access-denied.html`
* Redirect Status Code: `302`

redirects users to a custom access-denied page whenever the CDN generates a 403 response.

## Common Use Cases

### Geo Blocking

Display a custom message when access is restricted based on visitor location.

### IP Restriction

Provide additional information when requests are denied by access control policies.

### Security Controls

Present branded error pages instead of generic CDN error responses generated by edge-level security features.

## Important Notes

* This feature applies only to edge-generated error responses.
* Origin-generated error pages are not affected.
* The Error Page URL must remain accessible to users.
* Redirect loops should be avoided when hosting custom error pages on protected resources.
* Multiple status codes can be mapped to different error pages.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.