Show search and navigation.

 

Client Request Types Report

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.
AnalyticsThis product provides a variety of reports that range from basic CDN usage statistics to real-time data to in-depth trend analysis on key metrics. This suite consists of the following modules: Core, Custom, Advanced Content Analytics, Real-Time Statistics, and Edge Performance Analytics. - Edge Performance Analytics

The Client Request Types report indicates the type of requests that were made by HTTP clients (e.g., browsers). This report includes a donut chart that provides a sense as to how requests are being handled. Bandwidth and traffic information for each request type is displayed below the chart.

Request Type Description

Normal

This request type is reported when all of the following conditions are met:

  • The requested asset must be successfully delivered to a client.
  • The request cannot contain a revalidation or refresh header (as defined below).
This type of request will return a 200 OK status code to the client.

Refresh

This request type is reported when all of the following conditions are met:

  • The requested asset must be successfully delivered to a client.
  • The request must contain one of the following header values:
  • Cache-Control: no-cache
  • Pragma: no-cache

The use of one of the above directives forced the asset to be refreshed from the origin server. This type of request will return a 200 OK status code to the client.

Revalidation

This request type is reported when all of the following conditions are met:

  • The requested asset must be successfully delivered to a client.
  • The request must contain one of the following header values:
    • If-Modified-Since
    • If-None-Match

The status code that is returned by this request type is determined by whether the HTTP client's cached version of the requested asset matches the one stored on an edge server. If the HTTP client contains a cached version of the asset and it matches the version on an edge server, then a 304 Not Modified response code is returned to the client. Otherwise, a new version of the asset is retrieved from the origin server and a 200 OK response code is returned to the client.

Revalidation + Refresh

This request type is reported when all of the following conditions are met:

  • The requested asset must be successfully delivered to a client.
  • The request must contain both revalidation and refresh headers (as defined above).

The status code that is returned by this request type is determined by whether the HTTP client's cached version of the requested asset matches the one stored on the origin server. If the origin server contains the same version of the asset, then a 304 Not Modified response code is returned to the client. Otherwise, a new version of the asset is retrieved from the origin server and a 200 OK response code is returned to the client.

The data that was used to generate the chart, along with detailed bandwidth and traffic information, is displayed directly below it.

View a description for each of these metrics.