httpstatuses/contents/codes/422.md

19 lines
761 B
Markdown
Raw Normal View History

2015-11-06 22:55:41 +01:00
---
set: 4
code: 422
title: Unprocessable Entity
references:
"Rails HTTP Status Symbol": ":unprocessable_entity"
"Symfony HTTP Status Constant": "Response::HTTP_UNPROCESSABLE_ENTITY"
2015-11-06 22:55:41 +01:00
---
The server understands the content type of the request entity (hence a [415 Unsupported Media Type](/415) status code is inappropriate), and the syntax of the request entity is correct (thus a [400 Bad Request](/400) status code is inappropriate) but was unable to process the contained instructions.
For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.
---
* Source: [RFC4918 Section 11.2][1]
[1]: <http://tools.ietf.org/html/rfc4918#section-11.2>