# Add HTTP status code 450 to http module

**URL:** <https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837>\
**Category:** Ideas\
**Created:** [June 17, 2025, 5:18pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837 "2025-06-17T17:18:31Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharktide](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sharktide/32/27762_2.png) [@sharktide](https://discuss.python.org/u/sharktide)\
**Post date:** [June 17, 2025, 5:18pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/1 "2025-06-17T17:18:32Z")

</div>

As we have seen, Python supports a wide range of http codes, including all the IANA official codes + some additional ones such as 418 (The requested entity is a teapot incapable of brewing coffee).

**My point is:** If python supports 418 and aims to support others, it might be reasonable to support 450 (blocked by windows parental controls). Assuming we want to cover all bases and scenarios, adding this to http and the docs could be of _some_ use to people.

And before you answer “does anyone care about 450 that was a long time ago” Yes, people care. Some windows computers use it, and some websites now use it to indicate that they are functional but device restrictions won’t allow them to fulfill the request.

Also those who like to dig deep may have found this statement in the http docs:

> Supported, [IANA-registered status codes](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml)available in [http.HTTPStatus](https://docs.python.org/3/library/http.html#http.HTTPStatus) are:

This is to be ignored considering 418 is there and is being adressed in [#135625](https://github.com/python/cpython/pull/135625)

---

<div class="post-metadata">

**Author:** ![MegaIng](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/megaing/32/16162_2.png) [@MegaIng](https://discuss.python.org/u/MegaIng)\
**Post date:** [June 17, 2025, 5:27pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/2 "2025-06-17T17:27:42Z")

</div>

Is there any example except 418 that is supported by `http.HTTPStatus`?

418 is clearly registered at IANA and has an RFC behind it, even if it is a joke. 450 is listed as “unassigned”, not as “unused” like 418 is.

You repeatably saying “some additional ones” as if this is plural. But is it plural?

---

<div class="post-metadata">

**Author:** ![AA-Turner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/aa-turner/32/4979_2.png) [@AA-Turner](https://discuss.python.org/u/AA-Turner)\
**Post date:** [June 17, 2025, 5:38pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/3 "2025-06-17T17:38:27Z")

</div>

I agree, better to note that 418 is an exception than to begin supporting further unofficial/unregistered status codes.

A

---

<div class="post-metadata">

**Author:** ![elis.byberi](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/elis.byberi/32/35937_2.png) [@elis.byberi](https://discuss.python.org/u/elis.byberi)\
**Post date:** [June 17, 2025, 5:40pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/4 "2025-06-17T17:40:02Z")

</div>

> the 418 status code is reserved in the [IANA](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) [HTTP](https://www.rfc-editor.org/rfc/rfc9110.html#name-418-unused) Status Code Registry

---

<div class="post-metadata">

**Author:** ![MegaIng](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/megaing/32/16162_2.png) [@MegaIng](https://discuss.python.org/u/MegaIng)\
**Post date:** [June 17, 2025, 5:41pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/5 "2025-06-17T17:41:25Z")

</div>

> [@AA-Turner](#):
>
> I agree, better to note that 418 is an exception than to begin supporting further unofficial/unregistered status codes.

I don’t even think I agree that it’s unofficial or unregistered. It is listed officially, it’s just doesn’t have a “true” meaning behind it. (which doesn’t stop people from using it)

---

<div class="post-metadata">

**Author:** ![sharktide](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sharktide/32/27762_2.png) [@sharktide](https://discuss.python.org/u/sharktide)\
**Post date:** [June 18, 2025, 3:13am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/6 "2025-06-18T03:13:34Z")

</div>

I am assuming you want to start supporting the brew and when methods in http as outlined the rfc? I’ll raise an issue and make a PR 😉

---

<div class="post-metadata">

**Author:** ![Rosuav](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rosuav/32/3429_2.png) [@Rosuav](https://discuss.python.org/u/Rosuav)\
**Post date:** [June 18, 2025, 4:14am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/7 "2025-06-18T04:14:45Z")

</div>

> [@sharktide](#):
>
> I am assuming you want to start supporting the brew and when methods in http as outlined the rfc?

The list of methods in `http.HTTPMethods` is all from one source, plus PATCH. Notably, it does not include methods used by related services such as [WebDAV](https://datatracker.ietf.org/doc/html/rfc4918.html), which adds quite a few methods that won’t be relevant to the vast majority of HTTP users. WebDAV’s response codes _are_ included in `http.HTTPStatus` though. So if you want to push for the BREW method to be added on account of 418’s presence, for consistency you should also push for PROPFIND, MKCOL, LOCK, MOVE, etc, from RFC 4918.

I don’t think we need to do that. Being able to give explanations for response codes is a lot more useful than listing every possible HTTP verb that anyone has used. Keep in mind that you can always call [`request()`](https://docs.python.org/3/library/http.client.html#http.client.HTTPConnection.request) with an arbitrary method name, if you are in fact connecting to a coffeepot.

---

<div class="post-metadata">

**Author:** ![sharktide](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sharktide/32/27762_2.png) [@sharktide](https://discuss.python.org/u/sharktide)\
**Post date:** [June 18, 2025, 4:41am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/8 "2025-06-18T04:41:38Z")

</div>

That was intended to be funny, but now thinking about it, why _not_? _Some_ People might in fact find it useful to have methods such as LOCK, MOVE etc. in python. And in the event of calling `request()` with an arbitrary method name → Thats a messy implementation begging to be fixed.

And if we don’t want to add BREW, PROPFIND, and WHEN, isn’t our implementation of 418 a half-hearted work?

Just look at this: [GitHub - HyperTextCoffeePot/HyperTextCoffeePot: A real implementation of the HTCPCP Protocol for use on a Raspberry Pi..](https://github.com/HyperTextCoffeePot/HyperTextCoffeePot)

(and I may be crazy, feel free to tell me so)

---

<div class="post-metadata">

**Author:** ![Rosuav](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rosuav/32/3429_2.png) [@Rosuav](https://discuss.python.org/u/Rosuav)\
**Post date:** [June 18, 2025, 4:46am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/9 "2025-06-18T04:46:49Z")

</div>

> [@sharktide](#):
>
> (and I may be crazy, feel free to tell me so)

Yeah, you’re crazy. But let’s face it, most of us are, or we wouldn’t still be here.

TBH I think it’s more useful to have a translation table of potential responses than all of the possible verbs. If you’re going to attempt to BREW, or to LOCK, you’re going to need to know a lot of semantics; but if you attempt to do something on the wrong type of server, it’s useful to at least be able to translate a code into a description. From the flip side, if you’re writing a server and you get a verb you don’t know, all you have to do is return 405 and call it a night. \[1\] Given the enormous number of potential HTTP-adjacent verbs, it’s best to stick to a single definition of which ones are to be used, and for that, IANA’s repository seems like a good one to use.

* * *

1. Or call it a knight, which would be Sir 405.

---

<div class="post-metadata">

**Author:** ![sharktide](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sharktide/32/27762_2.png) [@sharktide](https://discuss.python.org/u/sharktide)\
**Post date:** [June 18, 2025, 6:42am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/10 "2025-06-18T06:42:15Z")

</div>

In that case, why are we including status codes but not their respective methods? That alone should be a warning flag for inconsistency. For example, people might see that we have included 418 and subsequently try to complete a BREW request. If we want to stick to IANA’s repository, we should remove 418 and WebDAV’s response codes. What if someone tries a LOCK request thinking we support WebDAV?

---

<div class="post-metadata">

**Author:** ![Rosuav](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/rosuav/32/3429_2.png) [@Rosuav](https://discuss.python.org/u/Rosuav)\
**Post date:** [June 18, 2025, 7:10am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/11 "2025-06-18T07:10:47Z")

</div>

> [@sharktide](#):
>
> In that case, why are we including status codes but not their respective methods?

> [@Rosuav](#):
>
> I think it’s more useful to have a translation table of potential responses than all of the possible verbs.

Did you read my previous post?

---

<div class="post-metadata">

**Author:** ![sharktide](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sharktide/32/27762_2.png) [@sharktide](https://discuss.python.org/u/sharktide)\
**Post date:** [June 18, 2025, 7:23am UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/12 "2025-06-18T07:23:23Z")

</div>

Yes, I did. But you aren’t getting my point:

Sure we can support 5 more methods if we wanted - imo it is more confusing right now than to have extra methods. And we can always document them clearly in a lookup table or whatever

Any quick google search can answer any questions people may have.

You have to admit that including something in one place but dropping its core component in the other makes no sense for this core reason

**if you seriously get a 418, chances are you want to use BREW or one of the others from the rfc** If we backed save418, we should have added at least the 418 methods a looong time ago

---

<div class="post-metadata">

**Author:** ![elis.byberi](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/elis.byberi/32/35937_2.png) [@elis.byberi](https://discuss.python.org/u/elis.byberi)\
**Post date:** [June 18, 2025, 4:24pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/13 "2025-06-18T16:24:48Z")

</div>

> [@sharktide](#):
>
> If we want to stick to IANA’s repository

Just to clarify, do you consider status codes 306 and 418 to be registered or not?

---

<div class="post-metadata">

**Author:** ![sharktide](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sharktide/32/27762_2.png) [@sharktide](https://discuss.python.org/u/sharktide)\
**Post date:** [June 18, 2025, 6:05pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/14 "2025-06-18T18:05:04Z")

</div>

IMO yes. I was going to comment about that but decided to hold off on the moment.

Considering the situation, (and the discussion title) we may as well talk about this.

Do you all think we should add 306? I’m +1 there, and

Another question I’m going to leave to you all: what should we do about 104? I’m +0 for that because even though IANA registered it, it is temporary and is currently in beta (trial ends in November)

EDIT: I take back what I said about 306. IANA is trying to deprecate and does not recommend the use of it due to “security concerns”

---

<div class="post-metadata">

**Author:** ![elis.byberi](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/elis.byberi/32/35937_2.png) [@elis.byberi](https://discuss.python.org/u/elis.byberi)\
**Post date:** [June 18, 2025, 6:58pm UTC](https://discuss.python.org/t/add-http-status-code-450-to-http-module/95837/15 "2025-06-18T18:58:39Z")

</div>

> [@sharktide](#):
>
> the discussion title [Add HTTP status code 450]

There exist many [unofficial codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Unofficial_codes). Since these codes are unofficial and subject to change without notice, there’s no requirement to keep track of them.
