-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Fix http status codes #20700
Fix http status codes #20700
Conversation
Update the message to be consistent with RFC 7168, and the rest of the statuses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, sorry, looks like Multiple Choices
is still correct as per https://tools.ietf.org/html/rfc7231#section-6.4.1
Perhaps change it back and adjust the comment to point to RFC7231 so this doesn't come up in the future?
bd71414
to
155efdf
Compare
The JS linter doesn’t pass, I need to rephrase my comment. I’m taking care of that later today! EDIT: Done. |
155efdf
to
01c089f
Compare
Adding comments to reference which RFC Node.js is following. Refs: https://tools.ietf.org/html/rfc7231#section-6.4.1 Refs: https://tools.ietf.org/html/rfc7168#section-2.3.3
What is this semver wise? 😄 |
That would be major right? I mean, we certainly wouldn't risk to break all the coffee pot controlling installations out there, would we? Those people deserve their coffee, even if they use an old version of the spec! 😄 |
Update the message to be consistent with RFC 7168. Add a note to "Multiple Choices" regarding RFC 7231 superseding RFC 7168. PR-URL: #20700 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yuta Hiroto <hello@hiroppy.me>t Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Landed in 464852b @mvasilkov and @aduh95 you should both be Contributors now! Thanks for the contribution. |
Update the message to be consistent with RFC 7168. Add a note to "Multiple Choices" regarding RFC 7231 superseding RFC 7168. PR-URL: #20700 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yuta Hiroto <hello@hiroppy.me>t Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Update the message to be consistent with RFC 7168. Add a note to "Multiple Choices" regarding RFC 7231 superseding RFC 7168. PR-URL: #20700 Reviewed-By: Anatoli Papirovski <apapirovski@mac.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Yuta Hiroto <hello@hiroppy.me>t Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
Fixes #20286.
I have used the @mvasilkov 's patch and @mithunsasidharan 's advice to make Node.js compliant with the latest HTCPCP-TEA (RFC 7168, an extension to HTCPCP to allow for pots to provide networked tea-brewing facilities).
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes