This repository was archived by the owner on Nov 10, 2025. It is now read-only.
Rename unprocessable_entity to unprocessable_content#815
Merged
DavidBiddle merged 1 commit intomainfrom Aug 15, 2025
Merged
Conversation
lfdebrux
approved these changes
Aug 15, 2025
When the 422 status was initially proposed in [RFC4918](https://datatracker.ietf.org/doc/html/rfc4918) (2007), it was called 'Unprocessable entity'. When it became a standard in [RFC9110](https://datatracker.ietf.org/doc/html/rfc9110) (2022), it was renamed 'Unprocessable content'. Rack now supports it as `:unprocessable_content` and has deprecated `:unprocessable_entity`. This commit updates it to use the new name.
DavidBiddle
force-pushed
the
rename-unprocessable-entity
branch
from
880c19d to
ee6a0a9
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this pull request solve?
When the 422 status was initially proposed in RFC4918 (2007), it was called 'Unprocessable entity'.
When it became a standard in RFC9110 (2022), it was renamed 'Unprocessable content'.
Rack now supports it as
:unprocessable_contentand deprecated:unprocessable_entityin v3.1.0. This commit updates it to use the new name.Things to consider when reviewing