Setting up traffic management for external HTTP(S) load balancers

External HTTP(S) Load Balancing supports several types of traffic management, such as URL redirects and rewrites. This document shows examples of using traffic management for some specific use cases. Other use cases are possible.

  • URL redirect. URL redirect (sometimes referred to as URL forwarding) redirects your domain's visitors to a different URL. For example, you can answer all incoming HTTP requests with responses instructing the client to convert to HTTPS requests. Redirects use HTTP status codes, such as 301 and 302.
  • URL rewrite. With URL rewrites, users and search engines can use URLs that are easier to remember and find. For example, you can allow users to use a URL like www.mydomain.com/static/images/, even though the actual content is hosted at www.myorigin.com/august_snapshot/images/.
  • Header-based and query parameter-based routing. With header-based and query parameter-based routing, your load balancer can intelligently route traffic based on HTTP headers and request URL parameters.

To understand how traffic management works for HTTP(S) Load Balancing, see Traffic management overview.

For detailed examples, see the following guides: