Response Headers

Applies To:
HTTP Large
HTTP Small
ADN

A user's request for content will generate a response from a server. This response consists of response headers. and a response body. The response headers generated for content requested through our CDN describe the response provided by an edge server. By default, our edge servers will include:

This topic describes the following:

Common Response Headers

Common response headers are listed below.

Response Header Description
Accept-Ranges

Indicates whether a server can accept range requests.

Default value: bytes

Note: The default value indicates that our servers can accept byte-range requests.

Cache-Control: max-age

Indicates the maximum length of time that a request is considered fresh. An edge server can serve fresh content directly from cache without having to perform a revalidation with the origin server.

Default value: 604800

Note: The default value indicates that the max-age for the requested content is 7 daysMax-age is defined in seconds. 604800 seconds = 7 days.

Content-Type

Indicates the content type for the response body. Sample content types are provided below.

  • text/plain

  • text/html

  • text/css

  • application/x-javascript

  • text/javascript

Date Indicates the date and time (GMT) on which the edge server returned a response.
Etag Indicates the entity tag (ETag) for the requested content. This ETag allows our edge servers to revalidate stale content. In other words, our edge servers will use ETag when checking with the origin server to see if there is a newer version of the requested content.
Expires Indicates the date and time (GMT) at which the response will be considered stale. By default, our edge servers must revalidate requests for stale content.
Last-Modified Indicates the date and time (GMT) at which the requested content was last updated.
Server

Provides information about the server that fulfilled the request.

Syntax (Customer Origin Server)

If a cached version of the requested content is not found, then the customer origin server will provide a response.

  • Server Response Header: If a Server response header is provided by the customer origin server, then our edge servers will forward it to the requester.
  • Missing Server Response Header: If the Server response header is missing, then information about the edge server that fulfilled the request will be returned to the requester. Please see the syntax for cached content.

Syntax (New Content & CDN Storage)

The following syntax applies for requests to CDN storage that have not been previously cached:

The terms used in the above syntax are defined below:

Syntax (Cached Content)

The following syntax applies for requests for cached content:

The terms used in the above syntax are defined below:

  • Platform: Indicates the platform on which the content was requested. The following codes are valid for this field:
    CodePlatform
    ECAcc HTTP Large
    ECS HTTP Small
    ECD Application Delivery Network (ADN)
  • POP: Indicates the POP that handled the request. View a list of POPs.
Vary

Identifies the variant that defines whether cached content can be served for future requests.

Key information:

  • Our network only supports a single variant called "Accept-Encoding." This value indicates that the Accept-Encoding request header determines whether cached content will be served.
  • By default, our edge servers only return this header when the requested content was previously cached.

Note: The Accept-Encoding request header identifies the type of compression requested by the client. An edge server may deliver the requested content immediately if the cached asset matches the requested compression method.

X-Cache

Indicates that a cached version of the requested content was served directly to the requester by an edge server.

This response header will be set to the following value:

  • HIT: Indicates that a cached version of the requested content was found and served to the user.
Content-Encoding

Indicates that a compressed version of the requested content was served to the requester.

This response header will indicate the asset's compression type (e.g., gzip, deflate, bzip2, etc.).

Content-Length Indicates the size of the response body in octets.

Viewing Response Headers

Response headers can be viewed using a variety of tools, such as:

Chrome Developer Tools

Chrome offers built-in developer tools through which you may view response headers.

To view response headers in Chrome

  1. Load Chrome.
  2. Press CTRL+SHIFT+I.
  3. Click Network.
  4. Request the desired content.
  5. Click on the name of the desired asset.
  6. Click on the Headers tab.

Tip: If you would like to submit this information to support personnel, right-click on the left-hand pane and then select the Save as HAR with content option. Attach the HAR file to your message.

Firebug

Firebug is a free browser add-on for Mozilla Firefox.

To view response headers in FireFox

  1. Load FireFox.
  2. Load Firebug by clicking on it from the FireFox toolbar.
  3. Click on the Net tab.
  4. Request the desired content.
  5. Click on the desired request.

Fiddler

Fiddler is a free web debugging tool. Although it has a variety of uses, it can be used to submit an HTTP request and view the corresponding response from the server. This tool provides a history of the requests submitted during the current session. This history, along with the verbose nature of this tool, makes it a useful troubleshooting tool through which you can diagnose the root cause of your issue.

Wget

Wget is a command-line tool that allows you to request content over FTP, HTTP, and HTTPS.

The following sample request will return header data for content delivered over the HTTP Large platform.

wget -SO Response.txt wpc.0001.{Base Domain}/000001/folder/asset.htm

cURL

cURL is a command-line tool that allows you to request content over FTP, HTTP, and HTTPS.

The following sample request will return header data for content delivered over the HTTP Large platform.

curl -s -D - http://wpc.0001.{Base Domain}/000001/folder/asset.htm -o $null