Opened 9 years ago
Closed 9 years ago
#35333 closed enhancement (fixed)
Add support for 451 http status code.
Reported by: | andizer | Owned by: | joehoyle |
---|---|---|---|
Milestone: | 4.5 | Priority: | low |
Severity: | normal | Version: | |
Component: | HTTP API | Keywords: | good-first-bug has-patch |
Focuses: | Cc: |
Description
It would be nice to add support for the newly 451 (HTTP 451 Unavailable For Legal Reasons) http response code.
I recently used the status_header
function and I saw this response code was missing.
See https://en.wikipedia.org/wiki/HTTP_451 for more details about the response code.
Attachments (1)
Change History (8)
#1
@
9 years ago
- Component changed from General to HTTP API
- Keywords needs-patch added
- Milestone changed from Awaiting Review to Future Release
#2
@
9 years ago
It isn't yet final (though very very close): https://datatracker.ietf.org/doc/draft-ietf-httpbis-legally-restricted-status/ Personally, I'm good with adding it now, but is there a good reason to wait?
#3
@
9 years ago
- Milestone changed from Future Release to 4.5
- Priority changed from normal to low
- Type changed from feature request to enhancement
This is fine to go in. We support other statuses whose RFCs are technically still in the proposal stage (see #16914).
Note: See
TracTickets for help on using
tickets.
Great idea @andizer, and welcome to WordPress Trac :)
Would you like to submit a patch for this?