Backends
Last updated
Last updated
In this section, you'll be able to view/add/edit or delete backend configurations.
Provisioning -> Backends
A backend (or origin server) is a server identified by an IP address or DNS name. This is where your CDN will fetch your content.
It's extremely important that all the output IPs from the CDN are able to reach the backend server, which means that any firewall or any other protection in your backend must allow for those IPs, which can be queried with this endpoint.
The actual IP of the client visiting your site will be displayed in the True-Client-IP HTTP header.
Remember that you don't need to create a new backend per site, and if two or more sites share that same backend then it can be shared.
The following options are required when creating or editing a backend.
Name
A descriptive and unique name for the backend.
IP / Origin
The origin server IP address or DNS name.
SSL
True if the connection is encrypted with (HTTPS).
Port
Port number where the origin server is listening for http/s connections, usually 80 or 443.
Healthcheck - Host
The host header to send to the backend server, for example if your backend server is running Apache, it would be the ServerName
or ServerAlias
value, for example: www.example.com
.
Healthcheck - URL
The URL where the healthcheck will send the request. The URL should point to a very lightweight resource that never changes, for example an empty txt file in your webserver.
Healthcheck - Status code
The expected status code. If the backend server answers with any other code, the backend will be marked as unhealthy and non-cached content will fail.