To resolve this issue, edit the default Location Header settings if the node returns a redirect location with the wrong protocol (HTTP/HTTPS), hostname, or port by setting a location!regex or location!replace expression.
location!regex - enter a regular expression to match the expected response from the node (a 301/302 redirection). You can use generic characters like (.*) to match parts of the expression
location!replace -enter a regular expression using $1 to $9 to redirect the response to a different object
If the location header does not match the location!regex regular expression, then there are a couple oflocation!rewrite options:
- Do nothing
- Rewrite the hostname to the request "host" header, and rewrite the protocol and port if necessary.
- Do not rewrite the hostname. Rewrite the protocol and port if the hostname matches the request's "Host" header (default)
You can set this in the Virtual Server. From the web UI:
Services > Virtual Servers > VS_Name > Edit > Connection Management > Location Header Settings
Note: This applies only to HTTP and HTTPS Decrypted Virtual Servers