Content-delivery API Errors

Content-delivery API Error Descriptions

core.internal-error-exception

An internal error has occurred during processing. Internal errors are not expected during normal system operation. Please contact the system administrator for more information

core.unauthorized

The request did not contain valid authorization. Obtain a valid authorization token from the authorization server and retry the request.

core.bad-request

A bad request was received by the system. The intent of the request could not be understood. Please inspect the requested operation and ensure it is properly formed

core.constraint-violation

The request received by the system contained more or more constraint violations. More detail about each violation should be included in the error response. Please check the error description for each respective error to learn more about each constraint violation.

core.not-null-violation

A required property was missing from the request. For many required properties, the system is able to determine a reasonable default. However, not all properties have defaults, and thus must be specified. Please retry the request with the property specified.

core.null-violation

A property required to not be specified for a request was present. Please retry the request withouth the property.

core.size-violation

A property was specified with a value that was outside the valid range for the property. The error message will often include the allowable minimum and maximum values. Please retry the request with a valid value.

core.max-violation

A property was specified with a value larger than it's allowable maximum. Please check the documentation for the range of allowable values for this property

core.min-violation

A property was specified with a value smaller than it's allowable minimum. Please check the documentation for the range of allowable values for this property

core.pattern-violation

A property value did not match the required pattern. Please check the documentation for this entity for rules about property naming.

core.entity-not-found

The requested entity could not be found.

core.entity-general-conflict

A non-specific conflict error occurred.

core.hostname-violation

The provided hostname was not properly formed.

core.ipv4-address-violation

The provided IPv4 address was not a well-formed address.

core.ipv6-address-violation

The provided IPv6 address was not a well-formed address.

core.mac-address-violation

The provided MAC address was not a well-formed address

core.non-existent-reference

The request referred to an instance of another entity that could not be found. Please check the configuration and locate the correct instance.

core.entity-referenced-conflict

An operation was attempted on an entity that is referenced by other entities. This would cause a problem, for example, if the request was attempting to delete such an entity.

core.entity-property-conflict

An attempt was made to set a property of an entity, but doing so would result in an invalid configuration. For example, an entity class might require unique values for some properties. If an entity with the given value already exists, then the system cannot accept the request.

core.invalid-parameter-violation

A field was passed in a request that did not meet formatting constraints. Please check the field and retry the request.

core.access-denied

The request attempted to access a resource on which the principal does not have authority.

core.illegal-operation

The requested operation is illegal

core.json-parse-error

The received payload could not be parsed

core.json-mapping-error

The received payload was structurally valid, but could not be processed or mapped onto internal data types. Check the content of the message for field type mismatches.

core.path-param-entity-field-mismatch

A parameter of the URI represents a field that is also specified in the request entity body. When specified in the body, the values of the URI parameter and entity field must match for the request to be consistent.

core.invalid-path-param

A path parameter specified in the request URI did not meet expectations.

core.assert-condition-violation

The provided value doesn't meet a predetermined condition (true/false).

core.readonly-property-violation

An attempt was made to modify a property that is read-only. Entity updates that specify the property must have a value matching the current value.

core.invalid-search-field-error

A search filter was presented that contained an unknown or unsearchable field in the query expression.

core.invalid-search-value-error

A search filter was presented that contained an invalid value for a field

core.invalid-search-expression-error

A search filter was presented that was not syntactically correct.

core.illegal-reference

An attempt was made to refer to one entity from another, but this operation was not deemed legal

core.entity-already-referenced

An attempt was made to refer to an entity that is already referred to, where only a single reference is allowed

core.entity-optimistic-concurrency-failure

An attempt was made to optimistically update an entity, but the update was not made successfully.

core.method-not-allowed-error

The requested resource does not support the presented HTTP method

core.resource-not-found-error

A resource was requested that does not exist. Please check documentation for supported resource paths.

core.unsupported-media-type-error

The request did not successfully complete content-type negotiation, as an unsupported content-type was presented.

core.general-client-error

A non-specific client side error occurred

core.service-unavailable-error

Service is temporarily unavailable

content-delivery.client-auth-without-certs-violation

Client auth was enabled in the request, but the certificate/key was not provided.

content-delivery.tls-certificate-chain-violation

A valid PEM formatted X.509 certificate chain with matching key is required. The system was unable to parse and determine validity of the provided values.

content-delivery.tls-certificate-violation

A valid PEM formatted X.509 certificate is required. The system was unable to parse and determine validity of the provided values.

content-delivery.tls-protocol-incompatible-ciphers-violation

A TLS protocol was specified to be used with incompatible ciphers.

content-delivery.ca-properties-violation

Certificate Authority related properties are not consistent.

content-delivery.tls-buffer-size-violation

Invalid TLS Buffer Size. Supported sizes include 4, 16, and 32.

content-delivery.origin-edge-params-violation

The edge parameters set on an origin are not consistent. For example, when setting the edge type to AEX, the edge hostname must be set to valid Akamai edge hostname.

content-delivery.origin-fast-reroute-params-violation

The fast reroute parameters set on an origin are not consistent.

content-delivery.invalid-healthcheck-url-violation

An invalid healthcheck URL was proposed.

content-delivery.invalid-shared-secret-map

Shared secret map must be valid. Keys must be non-null and non-empty.

content-delivery.http-response-code-violation

An invalid HTTP response code was provided. A valid HTTP response code can be a single value (such as 200), or in some cases, a range is allowed (such as 200-202). When using a range, the starting value must be before then ending value.

content-delivery.rules.dscp-value-violation

Must provide valid DSCP value

content-delivery.rules.duplicate-behavior-violation

A request was presented that contained duplicate element types for either defaultBehaviors or childBehaviors.

content-delivery.rules.fastcgi-invalid-param-map

FastCGI param map must be valid. Keys must be non-null and non-empty.

content-delivery.rules.uri-signature-protect-subfiles-filter-type-setting-violation

UriSignature protectSubFiles cannot be enabled when the UriFilterType on the rule is neither REGULAR_EXPRESSION_MATCH nor CASE_INSENSITIVE_REGULAR_EXPRESSION_MATCH

content-delivery.rules.uri-signature-protect-subfiles-protected-path-setting-violation

UriSignature protectSubFiles cannot be enabled unless protectedPathPattern is specified

200The error listing will be successfully returned.