Actions31
- Backup Actions
- Backup Share Actions
- Catalog Actions
- Cube Actions
- Domain Actions
- Snapshot Actions
- TCP Mapping Actions
- Webhook Actions
Domain → Update
AI-generatedSummary
Update a custom domain’s proxy settings on a Cube with a PATCH request. Set the origin scheme and optionally configure PROXY protocol behavior for the domain mapping.
Inputs
- Space ID (required) — ID of the Space that owns the Cube.
- Cube ID (required) — ID of the Cube.
- Domain Mapping ID (required) — Mapping ID for the domain, available from the Domain List operation.
- Origin Scheme — Choose HTTP or HTTPS for the edge-to-Cube connection. Choose Leave Unchanged to omit this field from the request. HTTP uses cleartext to the Cube; HTTPS is for a Cube that terminates TLS itself.
- Additional Fields → PROXY Protocol — Choose Off, V1, or V2. Off sends null to clear the setting; V1 and V2 send the corresponding PROXY protocol header. The app must accept the selected protocol on the Cube port, and all domains sharing that port need the same setting.
- Additional Fields → Confirm Mixed PROXY Protocol — Set true to save despite other domains on the same Cube port using a different PROXY protocol setting. Without confirmation, the API can reject the update with HTTP 409.
Output shape
A single API response item containing the updated domain mapping, if returned by the API.
Uses the required Krova API credential. The source defines a PATCH request but does not specify the response schema.