Configure request routing and forwarding

With request routing and forwarding enabled, you can specify alternate origin hostnames to forward the requests sent to your API. You can also create custom paths, specify non-default ports to pass the incoming requests through, and enter custom Host header values to be honored by the incoming requests.

How to

  1. On the API Definitions page, in the Registered APIs section, click the ellipsis icon () associated with the API configuration you want to configure request routing for.
  2. From the menu, select Manage versions.
  3. In the Version history panel, click the ellipsis icon () associated with the API configuration version you want to configure request routing for.
  4. From the list of delivery options, select Request routing and forwarding.
  5. On the Request routing and forwarding page, click Add a rule.
  6. In Rule name, enter a meaningful name for the rule.
  7. In Description, enter a description of the rule.
  8. In Rule conditions, select conditions that you want to trigger the rule with.
    The available conditions are Resource, Method, and Hostname. Conditions are mutually inclusive; a request needs to meet all conditions to trigger a rule.
  9. In the Destination details section, do these steps:
    1. In Origin hostname, enter an alternate origin hostname for the requests sent to this API. Click Verify to confirm if it’s signed with a certificate from an Akamai-managed CA.
    2. In Forward path, select one of these options:
      • To use the base path from the current API configuration, select Use default path.
      • To add a custom path to the API, select Add custom path and enter the path in the field that appears.
  10. Optional: In the Forward port field, specify the port for the requests sent to this API.
    If you leave this field empty, the requests will go to the default port indicated by the protocol in the alternative origin hostname.
  11. Optional: In the Forward Host header field, specify the Host header value for the requests sent to this API.
    If you leave this field empty, the Host header value will be the same as your alternative origin hostname.
  12. Optional: If you want to set up SureRoute for your alternate origin, follow Configure SureRoute for alternate origins.
  13. Click Save.