Summary of Error code 415: Unsupported Media Type
- How to fix 415 error?
- What is a 415 error?
- What does the 415 code mean?
- What is the reason code 415?
Search Results
AI Overview
AI Overview
A
415 Error is an HTTP status code that means “Unsupported Media Type”. The server refuses to accept the request because the format of the data (the “payload”) being sent is in a format not supported by the server for the given operation.
Common Causes
The error typically results from a mismatch between what the client sends and what the server is configured to accept. Common causes include:
Incorrect Content-Type header: The most frequent cause is when the Content-Type header in the request does not match the actual data format being sent. For example, sending JSON data but specifying text/plain as the content type.
Unsupported media type: The server’s configuration does not support the specific media type (MIME type) indicated in the request header. For instance, an API might only accept application/json but the client sends application/xml.
Incorrect Content-Encoding header: The data is compressed or encoded in a way the server does not understand or is not configured to decode (e.g., using gzip without the server having the necessary module enabled).
Typos or non-standard naming: Simple errors like using charset=UTF8 instead of the standard charset=UTF-8 can cause the server to reject the request.
How to Fix a 415 Error
Fixing the error involves ensuring the client and server agree on the data format and encoding.
Verify the Content-Type header: Double-check that the Content-Type header in your request is present and correctly specifies the format of the data you are sending (e.g., application/json for JSON data).
Check the server’s accepted types: Consult the API documentation or use tools like browser developer tools (in the Network tab) to see what media types the server actually expects or is willing to process. The Accept header in the server’s response can provide hints on the expected input format.
Ensure correct encoding: If you are using compression, ensure the Content-Encoding header is correct and that the server is configured to handle that specific encoding format.
Correct client-side configuration: If using a client-side tool or library (like Postman or a specific programming library), make sure it is configured to send the correct headers and data format. For example, in Postman, ensure you select “JSON” from the dropdown menu for the body type instead of the default “Text”.
Update server configuration: If you control the server, you may need to update its configuration files (e.g., in Apache or Nginx) to support the required media type or encoding.
415 Unsupported Media Type – KeyCDN Support
May 5, 2023 — 415 Unsupported Media Type. … As a website owner or developer, you know how frustrating it can be when your website doesn’t func…
KeyCDN
Resolving the HTTP 415 Error on Your Website – 10Web
Mar 1, 2024 — Resolving the HTTP 415 Error on Your Website * What is the HTTP 415 error? * Variations of this error. * Reasons why this error oc…
10Web
What Is a 415 Status Code? Causes, Fixes, and Best Practices
Jul 7, 2025 — Key Takeaways * The 415 status code indicates that the server can’t handle the format due to a wrong or missing header. * Always v…
IPRoyal.com
Show more
on 01-24-2014 01:32 PM
Hi,
I am from CUPM team at Cisco. I am trying to create a DistrilbutionList in UC. I got error code 415. The error message is: “= Unsupported Media Type. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.” Here is the code that I passed in the Post request. The input xmlDL to POST = <?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?><DistributionLists><DistributionList><Alias>turtle_1</Alias><DisplayName>Turtle One</DisplayName><IsPublic>true</IsPublic><Undeletable>false</Undeletable><DtmfAccessId>80001</DtmfAccessId><AllowContacts>false</AllowContacts><AllowForeignMessage>false</AllowForeignMessage><PartitionObjectId>/vmrest/partitions/f46a1105-1cfa-4be9-89eb-e43133add5f1</PartitionObjectId><PartitionURI>f46a1105-1cfa-4be9-89eb-e43133add5f1</PartitionURI><DistributionListMembersURI></DistributionListMembersURI></DistributionList></DistributionLists>
try{
JAXBContext ctx = JAXBContext.newInstance(com.cisco.uc713.rest.dlist.DistributionLists.class);
StringWriter writer = new StringWriter();
Marshaller marshaller = ctx.createMarshaller();
marshaller.marshal(dlsPojo, writer);
String xmlDL = writer.toString();
System.out.println(“&&& XML DistributionList = ” + xmlDL);
….
try{
//post a request
ClientResponse restResponse = webResource.accept(MediaType.APPLICATION_XML_TYPE).post(ClientResponse.class, xmlDL);
Status status = restResponse.getClientResponseStatus();
code = status.getStatusCode();
data = restResponse.getEntity(String.class);
}catch (ClientHandlerException chx){
….
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: