sure_route
Version: v2025-01-13 | Includes use: No |
---|
Behavior name: SureRoute
The SureRoute feature continually tests different routes between origin and edge servers to identify the optimal path. By default, it conducts races to identify alternative paths to use in case of a transmission failure. These races increase origin traffic slightly.
This behavior allows you to configure SureRoute along with a test object to improve delivery of non-cacheable no-store
or bypass-cache
content. Since edge servers are already positioned as close as possible to requesting clients, the behavior does not apply to cacheable content.
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" "sure_route" {
rules_v2025_02_18 {
name = "SureRoute"
comments = "Continuously tests different routes between origin and edge servers to identify the optimal path."
behavior {
sure_route {
enabled = true
type = "PERFORMANCE"
test_object_url = ""
to_host_status = "INCOMING_HH"
race_stat_ttl = "30m"
force_ssl_forward = false
enable_custom_key = false
}
}
}
}
"behaviors": [
{
"name": "sureRoute",
"options": {
"enabled": true,
"type": "PERFORMANCE",
"testObjectUrl": "",
"toHostStatus": "INCOMING_HH",
"raceStatTtl": "30m",
"forceSslForward": false,
"enableCustomKey": false
}
}
]
Options
Option | Description |
---|---|
enabled |
Enables the SureRoute behavior, to optimize delivery of non-cached content.
|
type |
Specifies the set of edge servers used to test routes. Value is one of:
|
custom_map |
If
type is CUSTOM_MAP this specifies the map string provided to you by Akamai Professional Services, or included as part of the Site Shield product.
|
test_object_url |
Specifies the path and filename for your origin's test object to use in races to test routes.
Akamai provides sample test objects for the Dynamic Site Accelerator and Web Application Accelerator products.
If you have more than one origin server deployed behind a load balancer, you can configure it to serve the test object directly on behalf of the origin, or route requests to the same origin server to avoid deploying the test object on each origin server. |
to_host_status |
Specifies which hostname to use. Value is one of:
|
to_host |
If
to_host_status is OTHER this specifies the custom Host header to use when requesting the SureRoute test object.
|
race_stat_ttl |
Specifies the time-to-live to preserve SureRoute race results, typically
30m If traffic exceeds a certain threshold after TTL expires, the overflow is routed directly to the origin, not necessarily optimally. If traffic remains under the threshold, the route is determined by the winner of the most recent race.
|
force_ssl_forward |
Forces SureRoute to use SSL when requesting the origin's test object, appropriate if your origin does not respond to HTTP requests, or responds with a redirect to HTTPS.
|
enable_custom_key |
When disabled, caches race results under the race destination's hostname. If enabled, use
custom_stat_key to specify a custom hostname.
|
custom_stat_key |
This specifies a hostname under which to cache race results. This may be useful when a property corresponds to many origin hostnames. By default, SureRoute would launch races for each origin, but consolidating under a single hostname runs only one race.
|
Updated about 1 hour ago