You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What specific section or headline is this issue about?
HTTP Status codes
What information was incorrect, unhelpful, or incomplete?
The status codes are presented in the documentation and their respective pages are presented as if both the status code (e.g. 500) and reason phrase (e.g. Internal Server Error) are both part of a single one required token.
However from what I can gather, according to the official standards, the reason phrase is optional in HTTP/1.1 and not supported in HTTP/2.
The reason phrases listed here are only recommendations -- they can be replaced by local equivalents or left out altogether without affecting the protocol.
What did you expect to see?
It should be made more clear that the status code and reason phrase are distinct, and noted that the reason phrase is optional.
Example: Instead of linking to a status code page like 400 Bad Request as it is currently it can be linked to like 400 (Bad Request).
Each individual page status page currently has a section titled "Status" where it presents the status code along with the reason phrase, this will also need to be adjusted and seperated into a "Status code" and "Recommended reason phraae" section.
Do you have any supporting links, references, or citations?
Josh-Cena
added
needs decision
The task needs consensus through discussion
and removed
needs triage
Triage needed by staff and/or partners. Automatically applied when an issue is opened.
labels
Jan 7, 2025
MDN URL
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
What specific section or headline is this issue about?
HTTP Status codes
What information was incorrect, unhelpful, or incomplete?
The status codes are presented in the documentation and their respective pages are presented as if both the status code (e.g. 500) and reason phrase (e.g. Internal Server Error) are both part of a single one required token.
However from what I can gather, according to the official standards, the reason phrase is optional in HTTP/1.1 and not supported in HTTP/2.
From RFC 9110:
What did you expect to see?
It should be made more clear that the status code and reason phrase are distinct, and noted that the reason phrase is optional.
Example: Instead of linking to a status code page like
400 Bad Request
as it is currently it can be linked to like400
(Bad Request).Each individual page status page currently has a section titled "Status" where it presents the status code along with the reason phrase, this will also need to be adjusted and seperated into a "Status code" and "Recommended reason phraae" section.
Do you have any supporting links, references, or citations?
https://stackoverflow.com/a/38655533
Do you have anything more you want to share?
No response
MDN metadata
Page report details
en-us/web/http/status
The text was updated successfully, but these errors were encountered: