Update a TLS delivery profileCopy Pageput https://{hostname}/api/content-delivery/v1/content-providers/{contentProviderId}/tls-delivery-profiles/{tlsDeliveryProfileId}Path ParamstlsDeliveryProfileIdintegerrequiredcontentProviderIdintegerrequiredBody ParamscaCertificatestringlength ≤ 10000caCertificateDetailsobjectcaCertificateDetails objectcaCertificateSecretIdstringciphersstringlength ≤ 65535contentProviderIdintegerrequired≥ 1crlstringlength ≤ 10000crlDetailsobjectcrlDetails objectdescriptionstringlength ≤ 256ecdhCurvestringenumSECP384R1PRIME256V1Allowed:SECP384R1PRIME256V1enableClientAuthbooleanDefaults to falsetruefalsenamestringrequiredlength between 1 and 128tlsBufferSizeintegerenum41632Allowed:41632tlsCertificatestringlength ≤ 10000tlsCertificateAndKeySecretIdstringtlsCertificateDetailsobjecttlsCertificateDetails objecttlsCertificateKeystringlength ≤ 10000tlsDeliveryProfileIdintegerrequired≥ 1tlsVerificationDepthinteger1 to 10Responses 200An HTTP 200 will signify the successful update of an tls-delivery-profile instance. 400An HTTP 400 will be returned if the request is badly formed or has constraint violations 403An HTTP 403 will be returned if the principal is not authorized to access the instance of blocklist that the request was made against. 404An HTTP 404 will be returned if the <<resourcePathName | !singularize>> with the specified entityId is not found. 409An HTTP 409 will be returned if the blocklist offered for create/update would lead to a conflicting state.Updated 19 days ago