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

Use updated name for HTTP 422 ("Unprocessable Content") in JSON error response schema #598

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arcanemachine
Copy link
Contributor

@arcanemachine arcanemachine commented Mar 1, 2024

The newest RFC on HTTP Semantics (RFC 9110) no longer uses the term Unprocessable Entity when describing HTTP 422, but now refers to it as Unprocessable Content.

This commit updates the default JSON error response schema to reflect this change.

Fixes #599

https://httpwg.org/specs/rfc9110.html#status.422

The newest RFC on HTTP Semantics (RFC 9110) no longer uses the term `Unprocessable Entity` when describing HTTP 422, but now refers to it as `Unprocessable Content`.

This commit updates the default JSON error response schema to reflect this change.

Ref: https://httpwg.org/specs/rfc9110.html#status.422
@zorbash
Copy link
Contributor

zorbash commented Mar 15, 2024

Following the discussion in elixir-plug/plug#1174 since this PR does not require any client changes we can consider it non-breaking.

@zorbash
Copy link
Contributor

zorbash commented Mar 15, 2024

[Suggestion] Update the references to Unprocessable Entity in the examples directory and rebase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default JsonErrorResponse schema references out-of-date name for HTTP 422
2 participants