Free tools

HTTP 415 Unsupported Media Type

The server will not accept this Content-Type. Free reference, no signup.

415 Unsupported Media Type

MeaningThe server will not accept this Content-Type.
WhenThe client sent text or form data to a JSON endpoint, or the reverse.
CausesA missing Content-Type: application/json header.
FixSend the content type the route documents.
RetryRetry after fixing the header.
Alert?Usually no. It is a client mistake unless your own integration starts sending the wrong type.

Runs in your browser. Nothing you enter is stored.

Most 415s are not an incident

It is a client mistake unless your own integration starts sending the wrong type.

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 415","level":"warning"}'
Get an API key All status codes

How to use it

  1. Read what 415 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 415 Unsupported Media Type means The server will not accept this Content-Type. Servers send it when The client sent text or form data to a JSON endpoint, or the reverse.

Common causes: A missing Content-Type: application/json header. The practical fix is: Send the content type the route documents.

Retry: Retry after fixing the header.

Alert on it? Usually no. It is a client mistake unless your own integration starts sending the wrong type.

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 415?

The server will not accept this Content-Type.

Should the client retry?

Retry after fixing the header.

Should I alert on it?

Usually no. It is a client mistake unless your own integration starts sending the wrong type.

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.

400 Bad Request The server could not understand the request. 401 Unauthorized The request is missing valid authentication. 403 Forbidden The server understood the request and refuses it. Cron Job Alert Script Wrap a command so a failed, slow, or finished cron job sends a Trigv alert.