Validate status code

APPLIES TO: All API Management tiers

The validate-status-code policy validates the HTTP status codes in responses against the API schema. This policy may be used to prevent leakage of backend errors, which can contain stack traces.

Policy statement

<validate-status-code unspecified-status-code-action="ignore | prevent | detect" errors-variable-name="variable name">
    <status-code code="HTTP status code number" action="ignore | prevent | detect" />
</validate-status-code>

Attributes

Attribute	Description	Required	Default
unspecified-status-code-action	Action to perform for HTTP status codes in responses that aren’t specified in the API schema. Policy expressions are allowed.	Yes	N/A
errors-variable-name	Name of the variable in context.Variables to log validation errors to. Policy expressions aren't allowed.	No	N/A

Elements

Name	Description	Required
status-code	Add one or more elements for HTTP status codes to override the default validation action for status codes in responses.	No

status-code attributes

Attribute	Description	Required	Default
code	HTTP status code to override validation action for.	Yes	N/A
action	Action to perform for the matching status code, which isn’t specified in the API schema. If the status code is specified in the API schema, this override doesn’t take effect.	Yes	N/A

Actions

The content validation policies include one or more attributes that specify an action, which API Management takes when validating an entity in an API request or response against the API schema.

• An action may be specified for elements that are represented in the API schema and, depending on the policy, for elements that aren't represented in the API schema.

• An action specified in a policy's child element overrides an action specified for its parent.

Available actions:

Action	Description
ignore	Skip validation.
prevent	Block the request or response processing, log the verbose validation error, and return an error. Processing is interrupted when the first set of errors is detected.
detect	Log validation errors, without interrupting request or response processing.

Usage

• Policy sections: outbound, on-error
• Policy scopes: global, workspace, product, API, operation
• Gateways: classic, consumption, self-hosted

Usage notes

• This policy can only be used once in a policy section.

Logs

Details about the validation errors during policy execution are logged to the variable in context.Variables specified in the errors-variable-name attribute in the policy's root element. When configured in a prevent action, a validation error blocks further request or response processing and is also propagated to the context.LastError property.

To investigate errors, use a trace policy to log the errors from context variables to Application Insights.

Performance implications

Adding a validation policy may affect API throughput. The following general principles apply:

• The larger the API schema size, the lower the throughput will be.
• The larger the payload in a request or response, the lower the throughput will be.
• The size of the API schema has a larger impact on performance than the size of the payload.
• Validation against an API schema that is several megabytes in size may cause request or response timeouts under some conditions. The effect is more pronounced in the Consumption and Developer tiers of the service.

We recommend performing load tests with your expected production workloads to assess the impact of validation policies on API throughput.

Example

<validate-status-code unspecified-status-code-action="prevent" errors-variable-name="responseStatusCodeValidation" />

Validation errors

API Management generates content validation errors in the following format:

{
 "Name": string,
 "Type": string,
 "ValidationRule": string,
 "Details": string,
 "Action": string
}

The following table lists all possible errors of the validation policies.

• Details: Can be used to investigate errors. Not meant to be shared publicly.
• Public response: Error returned to the client. Does not leak implementation details.

When a validation policy specifies the prevent action and produces an error, the response from API management includes an HTTP status code: 400 when the policy is applied in the inbound section, and 502 when the policy is applied in the outbound section.

Name	Type	Validation rule	Details	Public response	Action
validate-content
	RequestBody	SizeLimit	Request's body is {size} bytes long and it exceeds the configured limit of {maxSize} bytes.	Request's body is {size} bytes long and it exceeds the limit of {maxSize} bytes.	detect / prevent
	ResponseBody	SizeLimit	Response's body is {size} bytes long and it exceeds the configured limit of {maxSize} bytes.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{messageContentType}	RequestBody	Unspecified	Unspecified content type {messageContentType} is not allowed.	Unspecified content type {messageContentType} is not allowed.	detect / prevent
{messageContentType}	ResponseBody	Unspecified	Unspecified content type {messageContentType} is not allowed.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
	ApiSchema		API's schema does not exist or it could not be resolved.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
	ApiSchema		API's schema does not specify definitions.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{messageContentType}	RequestBody / ResponseBody	MissingDefinition	API's schema does not contain definition {definitionName}, which is associated with the content type {messageContentType}.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{messageContentType}	RequestBody	IncorrectMessage	Body of the request does not conform to the definition {definitionName}, which is associated with the content type {messageContentType}. {valError.Message} Line: {valError.LineNumber}, Position: {valError.LinePosition}	Body of the request does not conform to the definition {definitionName}, which is associated with the content type {messageContentType}. {valError.Message} Line: {valError.LineNumber}, Position: {valError.LinePosition}	detect / prevent
{messageContentType}	ResponseBody	IncorrectMessage	Body of the response does not conform to the definition {definitionName}, which is associated with the content type {messageContentType}. {valError.Message} Line: {valError.LineNumber}, Position: {valError.LinePosition}	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
	RequestBody	ValidationException	Body of the request cannot be validated for the content type {messageContentType}. {exception details}	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
	ResponseBody	ValidationException	Body of the response cannot be validated for the content type {messageContentType}. {exception details}	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
validate-parameters / validate-headers
{paramName} / {headerName}	QueryParameter / PathParameter / RequestHeader	Unspecified	Unspecified {path parameter / query parameter / header} {paramName} is not allowed.	Unspecified {path parameter / query parameter / header} {paramName} is not allowed.	detect / prevent
{headerName}	ResponseHeader	Unspecified	Unspecified header {headerName} is not allowed.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
	ApiSchema		API's schema doesn't exist or it couldn't be resolved.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
	ApiSchema		API schema does not specify definitions.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{paramName}	QueryParameter / PathParameter / RequestHeader / ResponseHeader	MissingDefinition	API's schema does not contain definition {definitionName}, which is associated with the {query parameter / path parameter / header} {paramName}.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{paramName}	QueryParameter / PathParameter / RequestHeader	IncorrectMessage	Request cannot contain multiple values for the {query parameter / path parameter / header} {paramName}.	Request cannot contain multiple values for the {query parameter / path parameter / header} {paramName}.	detect / prevent
{headerName}	ResponseHeader	IncorrectMessage	Response cannot contain multiple values for the header {headerName}.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{paramName}	QueryParameter / PathParameter / RequestHeader	IncorrectMessage	Value of the {query parameter / path parameter / header} {paramName} does not conform to the definition. {valError.Message} Line: {valError.LineNumber}, Position: {valError.LinePosition}	The value of the {query parameter / path parameter / header} {paramName} does not conform to the definition. {valError.Message} Line: {valError.LineNumber}, Position: {valError.LinePosition}	detect / prevent
{headerName}	ResponseHeader	IncorrectMessage	Value of the header {headerName} does not conform to the definition. {valError.Message} Line: {valError.LineNumber}, Position: {valError.LinePosition}	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{paramName}	QueryParameter / PathParameter / RequestHeader	IncorrectMessage	Value of the {query parameter / path parameter / header} {paramName} cannot be parsed according to the definition. {ex.Message}	Value of the {query parameter / path parameter / header} {paramName} couldn't be parsed according to the definition. {ex.Message}	detect / prevent
{headerName}	ResponseHeader	IncorrectMessage	Value of the header {headerName} couldn't be parsed according to the definition.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{paramName}	QueryParameter / PathParameter / RequestHeader	ValidationError	{Query parameter / Path parameter / Header} {paramName} cannot be validated. {exception details}	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
{headerName}	ResponseHeader	ValidationError	Header {headerName} cannot be validated. {exception details}	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent
validate-status-code
{status-code}	StatusCode	Unspecified	Response status code {status-code} is not allowed.	The request could not be processed due to an internal error. Contact the API owner.	detect / prevent

The following table lists all the possible Reason values of a validation error along with possible Message values:

Reason	Message
Bad request	{Details} for context variable, {Public response} for client
Response not allowed	{Details} for context variable, {Public response} for client

Related policies

• Content validation

Next steps

For more information about working with policies, see:

• Tutorial: Transform and protect your API
• Policy reference for a full list of policy statements and their settings
• Policy expressions
• Set or edit policies
• Policy samples