About the Deliver page

The Deliver page is the key area of the web interface where you access your CDN services. From here, you can access the Service summary tab and Service configuration tab for each CDN service.

Before you begin

Be sure you know how to access the web interface controls before learning about each of the pages you'll encounter there.

About the Deliver page

The Deliver page provides a list of clickable links to all CDN services associated with your account. You can use the search box to search for a service by ID, name, or domain. Additionally, the Deliver page displays high-level details about each service including the active version number, the current requests per second, and a chart of the last hour of requests.

Clicking a link to a CDN service takes you to the Service summary tab, where you can review other general service details, and gives you access to the Service configuration tab, which contains the main controls for editing your service configurations.

About the Service summary tab

When you select a service from the Deliver page, the Service summary tab appears. From here, you can review general service details including the event log, duplicate (clone) service versions so you can edit them, and purge content.

The Service summary tab also allows you to compare differences between two configuration versions.

About the Service configuration tab

The Service configuration tab contains the main controls for editing your service configurations. Specifically you can:

• manage the domains used to route requests to a CDN service
• manage the hosts used as backends for a site and how they should be accessed
• manage the health checks that monitor backend hosts
• enable certain Fastly products for the service, if you are assigned the role of superuser or engineer. Note that this will result in changes to your monthly bill.
• manage various request and cache settings, headers, and responses that control how Fastly caches and serves content for a CDN service
• specify how logging should be performed and where server logs should be sent
• create custom Varnish configuration language (VCL) files
• specify how conditions are mapped and used for a service at various times (e.g., during request processing, when Fastly receives a backend response, or just before an object is potentially cached)

With the appropriate permissions, you can activate configuration changes immediately and roll back those changes just as quickly should they not have the intended effect.

What's next