< HTTP/1.1 510 Not Extended510 Not Extended (HTTP Extension Framework)
510 Not Extended comes from the experimental HTTP Extension Framework in RFC 2774, now historic. See what it meant and what to do if you hit it.
- Cacheable
- Only with explicit freshness
- Retry?
- No: add the required extension
- Usually sent by
- Origin server
- Spec
- RFC 2774 §7
On this page
TL;DR: 510 Not Extended belongs to RFC 2774, an experimental HTTP extension framework that went unused and was moved to Historic. A 510 today is a product-specific response you must read the body of, not a signal clients can act on in a standard way.
What it was for
RFC 2774 (2000) defined a way for HTTP messages to declare mandatory extensions, using Man and Opt headers with a URI naming the extension and a header-prefix. A server that required an extension the request had not declared answered 510, and the client was meant to resend the request including the declaration.
M-GET /resource HTTP/1.1
Host: example.com
Man: "http://example.com/ext/security"; ns=15
15-auth: token=abc123HTTP/1.1 510 Not Extended
Ext:
Content-Length: 0The mechanism needed new methods (M- prefix) and header handling in every client and intermediary, and it never caught on. The IANA registry still lists 510 with RFC 2774 as its reference, and the RFC was later reclassified as Historic.
What to do if you see one
- Check who sent it:
Server,Via,X-Powered-By, and the body. A real RFC 2774 response is empty or minimal and mentions anExtheader; anything else is a vendor reuse. - Read the vendor docs: some hosting stacks and appliances use 510 for their own conditions. The code does not tell you what.
- Do not retry. A 5xx suggests a server problem, but a 510 is not a transient failure. Clients with no specific handling for a 5xx code treat it like 500.
- If you maintain a service and consider emitting 510, do not. Use 501 for unsupported functionality, 400 for a malformed or missing request element, or 426 when the client must upgrade protocol.
Why the code number is still around
The IANA registry keeps assigned codes listed, so 510 stays there even though the mechanism that defined it is dead. Libraries ship it in their enumerations (Python’s http.HTTPStatus.NOT_EXTENDED, Go’s http.StatusNotExtended) for completeness, and you can see it in API test suites that iterate over every status. That is different from being in use.
If you find it in logs of an old appliance or proxy, the likelier reading is that a vendor picked an unused 5xx number for its own error. Compare the timestamp with deployments, check for a custom error page, and ask the vendor, since nothing in the protocol can tell you what it means.
Try it with curl
510 Not Extended belongs to the HTTP Extension Framework (RFC 2774, an experimental RFC that was never widely adopted), so no mainstream server sends it. If you meet one, curl -i is enough to read the status and any headers it carries.
curl -i https://legacy.example.com/resourceRelated
Frequently asked questions
What does 510 Not Extended mean?
Under RFC 2774, the server required an HTTP extension that the request did not declare, using the mandatory extension mechanism. The client was expected to resend the request with the extension declaration. The framework is historic and almost nobody implements it.
Why am I getting 510 from a modern website?
It is probably not the RFC 2774 meaning. Some products reuse 510 for their own errors, so read the response body and headers, and find which server or gateway produced it with Server and Via.
How do I fix 510?
There is no standard fix on the client. If it is from a specific product, consult its documentation. If you control the server, replace it with a more conventional status such as 400 or 501, because no client knows how to react to 510.
Sources
Related
501 Not Implemented
The server doesn't support the functionality required to fulfill the request. Learn about unimplemented features.
504 Gateway Timeout: nginx, ALB and Cloudflare Fixes
Fix 504 Gateway Timeout: nginx proxy_read_timeout (60s default), ALB 60s idle, API Gateway 29s, Cloudflare 524 at 125s, with error-log strings and curl timing.
505 HTTP Version Not Supported
Learn what 505 HTTP Version Not Supported means when servers reject protocol versions. Understand HTTP/1.1, HTTP/2 compatibility and version negotiation.
506 Variant Also Negotiates
506 Variant Also Negotiates is a server configuration error in transparent content negotiation (RFC 2295). See what triggers it in Apache and how to fix it.