Added the right revision date for status code registry #15796
Conversation
|
Indeed, we can update the list of official HTTP status codes, but just changing the date is not enough. For instance, the 418 status code has been removed (yep, no more teapot). |
|
ok, working on it |
|
@fabpot done, I am just not sur about the |
|
👍 |
| 417 => 'Expectation Failed', | ||
| 418 => 'I\'m a teapot', // RFC2324 |
There was a problem hiding this comment.
this can't be done in 2.3. Removing the key is a BC break in case someone accesses it in the public array
There was a problem hiding this comment.
I didn't see that as IMO you should not access it directly. So I should do it in master right ?
There was a problem hiding this comment.
BC break of HTTP Code 418 fixed with #16585
|
Merging it in 2.8 |
|
Thank you @dupuchba. |
…dupuchba) This PR was submitted for the 2.3 branch but it was merged into the 2.8 branch instead (closes #15796). Discussion ---------- Added the right revision date for status code registry | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | License | MIT It's just a doc-fix. Last updated status codes were not the right ones, not very useful though but you can merge it :-). http://www.iana.org/assignments/http-status-codes/ Commits ------- 07d08c4 Added the right revision date for status code registry
It's just a doc-fix.
Last updated status codes were not the right ones, not very useful though but you can merge it :-).
http://www.iana.org/assignments/http-status-codes/