Configure SureRoute for alternate origins
In API Definitions, you configure SureRoute settings for each alternate origin you set up in request routing and forwarding. SureRoute tests multiple routes between an edge server and your origin to identify an optimal path for performance and establish alternative routes in cases of potential request failures.
- On the Request routing and forwarding page, click Add a SureRoute definition.
- From Origin, select the alternate origin hostname you provided in your rule definition.
In SureRoute test
object, enter the path and filename of the test object on your
alternate origin for SureRoute to use in races to test routes.
For example: /akamai/testobject.html
In Cache life for race results, set the time-to-live
(TTL) to hold the SureRoute race results.
Races only run when certain thresholds are hit. If traffic drops below the thresholds, the edge server continues to use the last race results to determine the optimal route until this TTL expires. When traffic next increases over the thresholds, the edge server uses the direct route until SureRoute determines a new optimal route. The standard setting is 30 minutes.
If you want to force SureRoute to use SSL when requesting the test object from
your alternate origin, enable Force SSL for races.
Enable this when your origin does not respond to HTTP requests, or responds with a redirect to HTTPS.
- In Race results key, select whether to store race results under the race destination's hostname or under a custom hostname.