Skip to content

Update status code 422 for matching rfc9110 #24866

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 26, 2023
Merged

Update status code 422 for matching rfc9110 #24866

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion files/en-us/web/api/history_api/example/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ const ajaxRequest = new (function () {
415: "Unsupported Media Type",
416: "Requested Range Not Satisfiable",
417: "Expectation Failed",
422: "Unprocessable Entity",
422: "Unprocessable Content",
423: "Locked",
424: "Failed Dependency",
425: "Unassigned",
Expand Down
6 changes: 3 additions & 3 deletions files/en-us/web/http/status/422/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: 422 Unprocessable Entity
title: 422 Unprocessable Content
slug: Web/HTTP/Status/422
tags:
- Client error
Expand All @@ -14,7 +14,7 @@ spec-urls: https://httpwg.org/specs/rfc9110.html#status.422
{{HTTPSidebar}}

The HyperText Transfer Protocol (HTTP)
**`422 Unprocessable Entity`** response status code indicates
**`422 Unprocessable Content`** response status code indicates
that the server understands the content type of the request entity, and the syntax of
the request entity is correct, but it was unable to process the contained instructions.

Expand All @@ -23,7 +23,7 @@ the request entity is correct, but it was unable to process the contained instru
## Status

```http
422 Unprocessable Entity
422 Unprocessable Content
```

## Specifications
Expand Down
2 changes: 1 addition & 1 deletion files/en-us/web/http/status/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ The status codes listed below are defined by [RFC 9110](https://httpwg.org/specs
- {{HTTPStatus(421, "421 Misdirected Request")}}
- : The request was directed at a server that is not able to produce a response.
This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.
- {{HTTPStatus(422, "422 Unprocessable Entity")}} ({{Glossary("WebDAV")}})
- {{HTTPStatus(422, "422 Unprocessable Content")}} ({{Glossary("WebDAV")}})
- : The request was well-formed but was unable to be followed due to semantic errors.
- {{HTTPStatus(423, "423 Locked")}} ({{Glossary("WebDAV")}})
- : The resource that is being accessed is locked.
Expand Down