Managing HTTP Redirects

The HTTP Redirect service allows you to redirect HTTP traffic to another URL. You can use HTTP Redirect to:

  • Redirect all HTTP traffic for an entire zone to another zone. For example, if a company owns example.net and example.com, HTTP Redirect lets the company redirect all HTTP traffic for example.net to example.com. This is a one-to-one mapping; wildcards are not supported.
  • Redirect a specific subdomain to an HTTP URL. For example, test.example.com can be redirected to http://example.net/test/test.php.
  • Redirect a subdomain to a URL with a port number. For example, camera.example.com can be redirected to http://office.example.com:8080 so a user can view their camera system without typing in the port number each time.
  • Permanently redirect a domain name that has been deprecated by displaying a 301 response code. Permanently redirecting a domain name informs search engines and browsers what to do with the information.

Required IAM Policies

To work with HTTP Redirects, you need to have a user login to the Console, and your user needs sufficient authority (by way of an IAM policy) to perform all the instructions that follow. If your user is in the Administrators group, you have the required authority.

If your user is not, then a policy like this would allow a specific group to manage HTTP Redirects:

Allow group <GroupName> to manage http-redirects in compartment <CompartmentName>

If you're new to policies, see Getting Started with Policies and Common Policies. For more details about policies for HTTP Redirect, see Details for the WAF Service.

Using the Console

To create an HTTP redirect
To edit an HTTP redirect
To delete an HTTP redirect
To move an HTTP redirect to another compartment

Using the API

Use the following operations to manage your HTTP redirect zones: