HTTP 426 – Upgrade Required
The server refuses to perform the request using the current protocol and wants an upgrade.
Common use case
Used to force clients from plain HTTP onto a newer protocol, e.g. requiring TLS or HTTP/2 before continuing.
Example
HTTP/1.1 426 Upgrade Required
Upgrade: TLS/1.2, HTTP/1.1
History
Part of RFC 2817 (2000), which defined the Upgrade mechanism for negotiating TLS over an existing HTTP connection.
Did you know?
It is the mirror image of 101 Switching Protocols - 101 says "ok, switching now", while 426 says "you must switch before I'll continue".