HTTP 201 Created vs 415 Unsupported Media Type
HTTP 201 (Created) is a 2xx Success response, while 415 (Unsupported Media Type) is a 4xx Client Error response. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. In contrast, 415 means that the server refuses to accept the request because the Content-Type is not supported.
Beschreibung
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
Wann Sie es sehen
After successfully creating a new user, post, order, or other resource via a REST API.
Wie man es behebt
No fix needed. Check the Location header for the URL of the new resource.
Beschreibung
The server refuses to accept the request because the Content-Type is not supported.
Wann Sie es sehen
When sending JSON to an endpoint that only accepts XML, or missing the Content-Type header.
Wie man es behebt
Set the correct Content-Type header matching the data format you're sending.
Wesentliche Unterschiede
201 is a 2xx Success response, while 415 is a 4xx Client Error response.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
HTTP 415: The server refuses to accept the request because the Content-Type is not supported.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
You encounter 415 when when sending JSON to an endpoint that only accepts XML, or missing the Content-Type header.
Wann welchen verwenden
For 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 415 (Unsupported Media Type): Set the correct Content-Type header matching the data format you're sending.