Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
xpe opened this issue Jan 2, 2024 · 4 comments
Closed

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

xpe opened this issue Jan 2, 2024 · 4 comments
Labels
closed: question A user misinterpretation or support question. No action required. Content:HTTP HTTP docs

Comments

@xpe
Copy link

xpe commented Jan 2, 2024

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
@xpe xpe added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Jan 2, 2024
@github-actions github-actions bot added the Content:HTTP HTTP docs label Jan 2, 2024
@Josh-Cena
Copy link
Member

This was changed in #24866. You can check the more up-to-date links there. (The MDN page also has a spec link to RFC9110.)

@Josh-Cena Josh-Cena closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2024
@Josh-Cena Josh-Cena added closed: question A user misinterpretation or support question. No action required. and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Jan 13, 2024
@xpe
Copy link
Author

xpe commented Jan 27, 2024

I stand corrected! Thanks!

@albannurkollari
Copy link

Hi. I just encountered into this mismatch too. Too my surprise, the official document stand correct with the MDN one but at least in Chrome all 422 are labelled as Unprocessable Entity.

Do you reckon this is a Chrome issue? @Josh-Cena
Thanks in advance!

@Josh-Cena
Copy link
Member

Yeah, very likely. I'm on vacation so I can't check, but it would be helpful to search through Chrome issues and maybe send one if nothing comes up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: question A user misinterpretation or support question. No action required. Content:HTTP HTTP docs
Projects
None yet
Development

No branches or pull requests

3 participants