The OCID of the HTTP Redirect's compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
The user-friendly name of the HTTP Redirect. The name can be changed and does not need to be unique.
The domain from which traffic will be redirected.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the HTTP Redirect.
The current lifecycle state of the HTTP Redirect.
The response code returned for the redirect to the client. For more information, see RFC 7231. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The redirect target object including all the redirect data.
The date and time the policy was created, expressed in RFC 3339 timestamp format.
The details of a HTTP Redirect configuration to allow redirecting HTTP traffic from a request domain to a new target.
*Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.