HTTP 505 HTTP Version Not Supported

HTTP 505 HTTP Version Not Supported indicates the server does not support the HTTP protocol version used in the request. In practice, this is extremely rare since modern servers support HTTP/1.0, HTTP/1.1, and HTTP/2. You might encounter it when: connecting to a legacy server that only supports HTTP/1.0, sending HTTP/2 to a server that only accepts HTTP/1.1, or when malformed requests are interpreted as an unknown HTTP version.

Debug HTTP 505 live
Analyze real 505 behavior — headers, caching, CORS, redirects
Open Inspector →

Try it (live endpoint)

Response includes the status code, standard headers (including Content-Type), and a small diagnostic JSON body describing the request and returned status.

Simulator URL (copy in the app after load — not a normal link):

https://httpstatus.com/api/status/505

Example request:

curl -i "https://httpstatus.com/api/status/505"
Try in playground

Meaning

The server does not support the HTTP protocol version used in the request.

What it guarantees
  • The server (or an upstream) failed to fulfill a valid request.
What it does NOT guarantee
  • The failure is permanent.
  • Immediate retries are always safe or effective.

When to use this status

  • Unhandled errors or bugs in request handling.
  • Upstream dependency failures.
  • Timeouts, overload, or infrastructure instability.

When NOT to use this status (common misuses)

Returning 5xx for client validation errors.
Clients retry unnecessarily; traffic spikes and costs increase.
Returning 500 without stable error identifiers/correlation.
SRE triage slows down; alerting becomes noisy and hard to act on.
Returning 503/504 without retry guidance.
Clients hammer the service or give up too early; cascading failures worsen.

Critical headers that matter

Content-Type
Defines error body format (JSON/text/problem+json).
Clients can’t parse structured errors; observability loses fidelity.
Cache-Control
Prevents caching transient errors unless intended.
CDNs cache failures; prolonged user-visible outages.

Tool interpretation

Browsers
Displays an error state; devtools exposes status and headers. Cache headers can accidentally cache error documents.
API clients
Classifies as failure; retry policy depends on idempotency and code class. Structured errors improve handling.
Crawlers / SEO tools
Persistent failures reduce crawl rate; soft-404 patterns cause indexing instability.
Uptime monitors
Typically alerts based on rate/threshold. Consistent classification reduces false positives.
CDNs / reverse proxies
May cache errors if misconfigured; respects Cache-Control and can serve stale on origin failure.

Inspector preview (read-only)

On this code, Inspector focuses on semantics, headers, and correctness warnings that commonly affect clients and caches.

Signals it will highlight
  • Status semantics vs method and body expectations
  • Header sanity (Content-Type, Cache-Control, Vary) and evidence completeness
  • Error cacheability and retry guidance signals
Correctness warnings
No common correctness warnings are specific to this code.

Guided Lab outcome

  • Reproduce HTTP 505 HTTP Version Not Supported using a controlled endpoint and capture the full exchange.
  • Practice distinguishing status semantics from transport issues (redirects, caching, proxies).
  • Learn to attribute failures to origin vs upstream and apply safe retry/backoff decisions.

Technical deep dive

HTTP 505 HTTP Version Not Supported represents a specific server-side condition that requires different handling than other 5xx errors. Understanding the precise cause helps operations teams diagnose and resolve issues faster. Monitoring systems should distinguish 505 from other 5xx codes for accurate alerting and diagnosis.

Real-world examples

Production 505 HTTP Version Not Supported incident
A production system returns 505 HTTP Version Not Supported. The operations team triages based on the specific status code: specific server condition requiring investigation.
Load balancer returning 505
A load balancer returns 505 to clients. For 505 specifically, this typically indicates a specific protocol or configuration issue.
Client retry logic for 505
A client receives 505 HTTP Version Not Supported. This is typically not retryable — it indicates a configuration or protocol issue that requires server-side fixes.

Framework behavior

Express.js (Node)
Express: uncaught exceptions in route handlers result in 500 by default. Use error middleware: app.use((err, req, res, next) => { res.status(err.status || 500).json({ error: 'Internal Server Error' }); });
Django / DRF (Python)
Django: unhandled exceptions return 505 through custom middleware or exception handling. Custom error views: handler500 = 'myapp.views.server_error'.
Spring Boot (Java)
Spring Boot: @ControllerAdvice can map specific exceptions to 505.
FastAPI (Python)
FastAPI: Use custom exception handlers to return 505 with appropriate error messages.

Debugging guide

  1. Check server configuration and protocol support
  2. Verify the error is reproducible — transient 505 errors may indicate intermittent issues like memory pressure or connection pool exhaustion
  3. Check recent deployments — a new deploy is the most common cause of sudden 505 spikes
  4. Review server resource utilization (CPU, memory, disk, connections)
  5. Test with curl -v to see the full response including headers — some 505 responses include diagnostic headers

Code snippets

Node.js
// Handle 505 HTTP Version Not Supported
process.on('unhandledRejection', (reason) => {
  console.error('Unhandled rejection:', reason);
});

app.use((err, req, res, next) => {
  console.error(`${req.method} ${req.url}:`, err.stack);
  res.status(err.status || 500).json({
    error: process.env.NODE_ENV === 'production'
      ? 'Internal Server Error'
      : err.message,
    requestId: req.id
  });
});
Python
from fastapi import FastAPI, Request
from fastapi.responses import JSONResponse
import logging

logger = logging.getLogger(__name__)

@app.exception_handler(Exception)
async def server_error_handler(request: Request, exc: Exception):
    logger.error(f'{request.method} {request.url}: {exc}',
                 exc_info=True)
    return JSONResponse(
        status_code=505,
        content={'error': 'HTTP Version Not Supported', 'request_id': request.state.id}
    )
Java (Spring)
@ControllerAdvice
public class GlobalErrorHandler {
    private static final Logger log = LoggerFactory.getLogger(
        GlobalErrorHandler.class);

    @ExceptionHandler(Exception.class)
    public ResponseEntity<ErrorResponse> handleException(
            Exception ex, HttpServletRequest req) {
        log.error("{} {}: {}", req.getMethod(),
                  req.getRequestURI(), ex.getMessage(), ex);
        return ResponseEntity.status(505)
            .body(new ErrorResponse("HTTP Version Not Supported",
                "An unexpected error occurred"));
    }
}
Go
func errorMiddleware(next http.Handler) http.Handler {
	return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
		defer func() {
			if err := recover(); err != nil {
				log.Printf("%s %s: %v\n%s",
					r.Method, r.URL, err, debug.Stack())
				w.WriteHeader(505)
				json.NewEncoder(w).Encode(map[string]string{
					"error": "HTTP Version Not Supported",
				})
			}
		}()
		next.ServeHTTP(w, r)
	})
}

FAQ

What causes 505 HTTP Version Not Supported errors?
Specific conditions related to HTTP Version Not Supported that require server-side investigation.
Should clients retry on 505 HTTP Version Not Supported?
Generally no. 505 HTTP Version Not Supported typically indicates a configuration issue that wont resolve on retry.
How should 505 HTTP Version Not Supported be monitored?
Track 505 error rate as a percentage of total requests. Alert on sustained rates above baseline (e.g., >1% for 5 minutes). Include error classification in dashboards to distinguish between different failure modes.
What information should a 505 response include?
In production: a generic error message, a request ID for correlation, and optionally a Retry-After header. Never include stack traces, internal paths, database errors, or configuration details. In development: full error details are acceptable. Always log the full error server-side with the request ID.

Client expectation contract

Client can assume
  • The server or an upstream failed to fulfill the request.
Client must NOT assume
  • Immediate retries are always safe or effective.
Retry behavior
Retry idempotent requests with backoff; avoid retries for non-idempotent writes unless you have idempotency keys.
Monitoring classification
Server error
Alert on rate and duration; ensure CDNs do not cache transient failures.

Related status codes

504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
506 Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference.

Explore more

Related tools
Related utilities