What 505 means
The server doesn’t support, or won’t use, the major HTTP version in the request.
When servers send it
Rarely seen. Usually a malformed request line, or a very old or very unusual client.
Common causes
- A malformed request line, such as a stray space in the URL making the version unreadable.
- A client sending an HTTP version the server doesn’t speak.
How to fix it as a developer
- Check that URLs in raw requests are properly encoded: a literal space in the path breaks the request line.
- Make sure custom HTTP clients send
HTTP/1.1.
How to fix it as a visitor
- Update your browser. If it still happens, contact the site.
Related codes
- 400 Bad Request: The server can’t or won’t handle the request because something in it is malformed.
- 426 Upgrade Required: The server won’t handle this request over the current protocol. The Upgrade header says which to switch to.
- 501 Not Implemented: The server doesn’t support the feature needed to answer, such as an unknown request method.
Where it’s defined
505 HTTP Version Not Supported is defined in RFC 9110, section 15.6.6. It’s a 5xx code, the server error class: the server, or something behind it, failed to deal with a valid request.
Other 5xx codes
500 Internal Server Error · 501 Not Implemented · 502 Bad Gateway · 503 Service Unavailable · 504 Gateway Timeout · 511 Network Authentication Required · 520 Web Server Returned an Unknown Error · 521 Web Server Is Down · 522 Connection Timed Out · 523 Origin Is Unreachable · 524 A Timeout Occurred · 525 SSL Handshake Failed · 526 Invalid SSL Certificate
Or search them all in the HTTP status code list.