Redirect Handle From Origin
This setting is available for small, large and Aksela resource types.
Parameters | Description | Type | Required |
---|---|---|---|
organization_uuid | The created organization in Medianova Cloud Panel unit ID value. Path parameter. | String | Yes |
resource_uuid | The created resource in Medianova Cloud Panel unit ID value. Path parameter. | String | Yes
|
status_redirect_handle | Enables the opening and closing of the origin redirection process. | Bool | Yes |
handle_origin_rejection_error | Specifies which HTTP status codes the operation should be performed for. These codes are 301, 302, 303, 307, and 308. You can send all or any of them to perform the operation. | Array | Yes |
redirect_handle_request_headers | Allows adding a header for sending header information to the destination origin after redirection. | Array | No |
redirect_handle_request_headers.key | Specifies the name of the header to be sent to the destination origin. | String | Yes |
redirect_handle_request_headers.value | Specifies the value of the header to be sent to the destination origin. | String | Yes |
redirect_handle_add_headers | Allows adding a header for conveying a specific header to the user after redirection from the origin source. | Array | No |
redirect_handle_add_headers.key | Specifies the name of the header to be returned to the user after the redirection process. | String | Yes |
redirect_handle_add_headers.value | Specifies the value of the header to be returned to the user after the redirection process. | String | Yes |
Payload
{
"resource_uuid": "***",
"status_redirect_handle": true,
"handle_origin_rejection_error": [301,302,303,307,308],
"redirect_handle_request_headers": [
{
"key": "x-test-request",
"value": "request-header"
}
],
"redirect_handle_add_headers": [
{
"key": "x-test-add",
"value": "response-header"
}
]
}