Skip to main content
SiteIndex

4xx Client Error

415 Unsupported Media Type

The server does not support the request body's format.

Check a URL's HTTP status

What it means

The Content-Type header does not match what the endpoint accepts.

Common causes

  • Sending JSON without Content-Type: application/json.
  • Uploading an unsupported file type.

How to fix it

  1. Set the correct Content-Type header.
  2. Convert the file to a supported format.

Example response

HTTP/1.1 415 Unsupported Media Type
Content-Type: text/plain; charset=utf-8

Worked example

A client sends a request the server cannot fulfill as submitted. Check the response body and request details, correct the input or permissions, and retry only after the relevant issue is resolved.

How to read this response

  1. Find the status line in your browser's Network panel, API client, or server access log.
  2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
  3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 415
415 Unsupported Media Type: The server does not support the request body's format.
Common causes: 415
Sending JSON without Content-Type: application/json. Uploading an unsupported file type.
How to fix it: HTTP 415
Set the correct Content-Type header. Convert the file to a supported format.

Defined in RFC 9110.

Related codes

Tools