HTTP 208 Already Reported vs 415 Unsupported Media Type
HTTP 208 (Already Reported) is a 2xx Success response, while 415 (Unsupported Media Type) is a 4xx Client Error response. 208 indicates that used inside a DAV: propstat response element to avoid enumerating internal members of multiple bindings to the same collection repeatedly. In contrast, 415 means that the server refuses to accept the request because the Content-Type is not supported.
Description
Used inside a DAV: propstat response element to avoid enumerating internal members of multiple bindings to the same collection repeatedly.
When You See It
In WebDAV responses to avoid duplicate listings.
How to Fix
No fix needed. This prevents redundant data in multi-status responses.
Description
The server refuses to accept the request because the Content-Type is not supported.
When You See It
When sending JSON to an endpoint that only accepts XML, or missing the Content-Type header.
How to Fix
Set the correct Content-Type header matching the data format you're sending.
Key Differences
208 is a 2xx Success response, while 415 is a 4xx Client Error response.
HTTP 208: Used inside a DAV: propstat response element to avoid enumerating internal members of multiple bindings to the same collection repeatedly.
HTTP 415: The server refuses to accept the request because the Content-Type is not supported.
You encounter 208 when in WebDAV responses to avoid duplicate listings.
You encounter 415 when when sending JSON to an endpoint that only accepts XML, or missing the Content-Type header.
When to Use Which
For 208 (Already Reported): No fix needed. This prevents redundant data in multi-status responses. For 415 (Unsupported Media Type): Set the correct Content-Type header matching the data format you're sending.