Free tools

HTTP 505 HTTP Version Not Supported

The server refuses the HTTP version used in the request. Free reference, no signup.

505 HTTP Version Not Supported

MeaningThe server refuses the HTTP version used in the request.
WhenA client speaks a version the server will not accept.
CausesAn old client or a proxy speaking HTTP/0.9 or an unsupported major version.
FixUse the HTTP version the server supports.
RetryRetrying the same version will fail.
Alert?Usually no. Alert if a proxy change makes normal clients hit it.

Runs in your browser. Nothing you enter is stored.

Most 505s are not an incident

Alert if a proxy change makes normal clients hit it.

curl -sS -X POST https://api.trigv.com/v1/events \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $TRIGV_API_KEY" \
  -d '{"channel":"ops","title":"HTTP 505","level":"warning"}'
Get an API key All status codes

How to use it

  1. Read what 505 means before changing a retry loop.
  2. Check the common causes against the response body and the server log.
  3. Follow the retry note. Retrying a 400 with the same body will fail again.
  4. Alert only in the cases the verdict describes.

About this tool

HTTP 505 HTTP Version Not Supported means The server refuses the HTTP version used in the request. Servers send it when A client speaks a version the server will not accept.

Common causes: An old client or a proxy speaking HTTP/0.9 or an unsupported major version. The practical fix is: Use the HTTP version the server supports.

Retry: Retrying the same version will fail.

Alert on it? Usually no. Alert if a proxy change makes normal clients hit it.

Trigv is a push for the moment a status starts mattering, not a log of every response. If the code is one you should hear about, the snippet posts a single event with level error or warning. The status page itself does not call your API.

Questions

What is HTTP 505?

The server refuses the HTTP version used in the request.

Should the client retry?

Retrying the same version will fail.

Should I alert on it?

Usually no. Alert if a proxy change makes normal clients hit it.

How is this different from reading the spec?

The page adds a plain retry note and an alert verdict for people running the service, not only for people parsing the response.

500 Internal Server Error The server hit an unexpected error. 501 Not Implemented The server does not support this feature. 502 Bad Gateway A proxy got an invalid response from the upstream server. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.