5xx server errorDeprecated
510 Not Extended
The request is missing an HTTP extension declaration that the server requires before it will process the request.
What 510 Not Extended means
Defined in RFC 2774 (An HTTP Extension Framework). The framework was never widely adopted and the RFC is now marked Historic, so 510 is effectively obsolete.
Common causes
- A server built for the RFC 2774 extension framework receiving a request without the extension it needs.
- A custom server using 510 for its own purposes.
How to fix 510 Not Extended
- Read the response body for the extension the server wants.
- If you run the server, return a standard code such as 400 or 403 instead.
Example response
HTTP/1.1 510 Not Extended
Content-Type: text/plain; charset=utf-8
510 Not ExtendedHow to check for a 510 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 510) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 510:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 510 {
fmt.Println(res.Status)
}Specification
510 Not Extended is defined in RFC 2774, section 7.
Related status codes
- 501
The server does not support the functionality needed for the request, typically an HTTP method it does not recognise.
- 400
The server could not understand the request because something in it is malformed, like broken JSON, bad syntax or invalid headers.
- 426
The server refuses to handle the request over the current protocol, and its Upgrade header names the protocol to switch to.