- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 426 Upgrade Required
426 Upgrade Required
The server refuses the request over this protocol and names, in an Upgrade header, the protocol the client has to switch to.
- Class
- 4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
- Defined in
- RFC 9110
What it looks like
HTTP/1.1 426 Upgrade Required Upgrade: websocket Connection: Upgrade
What causes it
When an address only works over another protocol. A WebSocket server that receives an ordinary HTTP request is the common case: it answers 426 with Upgrade: websocket. A server could demand a newer version of HTTP or TLS in the same way.
What to do about it
Use the protocol that the Upgrade header names. If you opened a WebSocket address in the address bar of a browser or with curl, nothing is wrong: connect to it with a WebSocket client. If a WebSocket client gets a 426, a proxy on the way is probably dropping the Upgrade header before the request reaches the server.
Not to be confused with
| 101 Switching Protocols | The server agrees to switch, after the client offered. |
|---|---|
| 505 HTTP Version Not Supported | The server doesn't support the HTTP version of the request. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.
Other 4xx codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 423 Locked
- 424 Failed Dependency
- 425 Too Early
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons