chase_​redirects

Version: v2025-01-13Includes use: Yes

Behavior name: Chase Redirects

Controls whether the edge server chases any redirects served from the origin.

Note: This behavior is not compatible with Amazon Web Services and Google Cloud Storage authentication methods in the origin_characteristics behavior. If you're using any of these authentication methods, Chase Redirects gets disabled automatically.

Default behavior

These samples reflect the behavior's default settings. You can use these as is in your configurations or make adjustments based on the behavior's available options.

data "akamai_property_rules_builder" "chase_redirects" {
  rules_v2025_02_18 {
    name     = "Chase Redirects"
    comments = "Controls whether the edge server chases any redirects served from the origin."
    behavior {
      chase_redirects {
        enabled  = true
        limit    = 4
        serve404 = true
      }
    }
  }
}
"behaviors": [
  {
    "name": "chaseRedirects",
    "options": {
      "enabled": true,
      "limit": "4",
      "serve404": true
    }
  }
]

Options

Option Description
enabled
Allows edge servers to chase redirects.
limit
Specifies, as a string, the maximum number of redirects to follow.
serve404
Once the redirect limit is reached, enabling this option serves an HTTP 404 (Not Found) error instead of the last redirect.