Page tree
Skip to end of metadata
Go to start of metadata

Here is the list of all the Actions for HTTP Rules:

ActionDetails
Force Edge To Never Cache

Forces the CDN edge server to never cache the request. However, if the request is already cached (for example, if it was cached prior to setting up this rule), it will not be forced out of cache.

Force Client To Never Cache

Forces the client to never cache the request. This is achieved by removing all Cache-Control and Expires response headers, sending instead “Cache-Control: no-cache”.

Force Edge To Cache

Forces the CDN edge server to cache the request for a specified duration. This overrides any Cache-Control or Expires headers from the origin, even if they specify “private” or “no-cache”.

The value must be 1 second or longer.

Force Client To Cache

Forces the client to cache the request for a specified duration. This is achieved by removing all Cache-Control and Expires response headers, sending instead “Cache-Control: max-age=...”.

The value must be 1 second or longer.

Override Default Cache Validity

Changes the CDN edge server’s default validity period for origin responses that do not explicitly specify Cache-Control or Expires. Responses with Cache-Control or Expires headers are still honored.

The value must be 1 second or longer.

Forbid ClientReturns a simple 403 Forbidden response to the client.
Redirect Client

Returns a 302 Redirect response to the client, to the specified URL.

The URL must be specified in full, starting with http:// or https://

Set Request HeaderOverrides a request header to the origin. A header name and header value must be provided.
Set Response HeaderOverrides a response header to the client. A header name and header value must be provided.

Set Client IP In Request Header

Sets the client’s IP address in a request header to the origin. A header name must be provided.
Prepend Origin Directory

Prepends a directory to the URL when the edge server requests it from the origin.

Examples:

Prepend origin directory “images”

Client requests to edge: http://cdn.example.com/photo.jpg 

Edge requests to origin: http://cdn.example.com/images/photo.jpg

 

Prepend origin directory “/some/sub%20directory/”

Client requests to edge: http://cdn.example.com/some/file.txt

Edge requests to origin: http://cdn.example.com/some/sub%20directory/some/file.txt

A value must be provided (it cannot be empty).

Leading and trailing slashes from the directory are automatically stripped.

Special characters, such as spaces, must be percent-encoded.

Set Custom Origin

Overrides the origin that the edge server connects to.

Example:

Resource has origin “3.3.3.3”.

A rule is added such that if a URL starts with “/images/”, it sets a custom origin to “5.5.5.5”.

A value must be provided (it cannot be empty) and it must be a valid hostname or IP.

A custom origin port cannot be specified or overridden.

“Set Request Header” may be used in conjunction with this to set a correct Host header.

Passthrough HTTP Host Header to Origin

Goes back to the origin when the condition = true, during the first time, and the subsequent request (being cached in edge) will not go back to the origin again although the condition = true.

CDN edge server will only go back to the origin when the file does not exist (cache) in the edge server (for ALL scenario), and the feature ""passthrough http host header to origin" happens during the path from cdn edge --> origin. This feature is not about "making all requests goes back to origin", but "sending the host header info to origin".