Skip to content

Isn't "422 Unprocessable Entity" the correct name? #31454

@xpe

Description

@xpe

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/422

What specific section or headline is this issue about?

422 Unprocessable Content

What information was incorrect, unhelpful, or incomplete?

I believe the title "422 Unprocessable Content" is out of date. I think the correct title should be "422 Unprocessable Entity".

What did you expect to see?

"422 Unprocessable Entity"

Do you have any supporting links, references, or citations?

Per https://datatracker.ietf.org/doc/html/rfc4918#section-11.2

The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) 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.

I noticed this because the Rust http crate uses "Unprocessable Entity" as well:

    /// 422 Unprocessable Entity
    /// [[RFC4918](https://tools.ietf.org/html/rfc4918)]
    (422, UNPROCESSABLE_ENTITY, "Unprocessable Entity");

Do you have anything more you want to share?

I haven't followed the relevant RFCs closely in a while. Please educate me if I've gotten this wrong; if so, then the Rust http crate has gotten it wrong too.

MDN metadata

Page report details

Metadata

Metadata

Assignees

No one assigned

    Labels

    Content:HTTPHTTP docsclosed: questionA user misinterpretation or support question. No action required.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions