208 Already Reported
Inside a WebDAV multi-status response, this member was already listed earlier and its properties are not repeated.
At a glance
- Status code
- 208 Already Reported
- Class
- 2xx, success, the request was received and accepted
- Defined in
- RFC 5842
- Cacheable by default
- no
- Response body
- Appears inside a 207 body, not on its own.
In detail
A binding can make the same resource appear at several paths. Without 208 a deep PROPFIND across a collection with internal bindings would enumerate the same resource repeatedly and the response would grow without bound.
Only meaningful inside a 207 body produced by a server that implements WebDAV bindings. Nothing else should emit it.
A client walking a 207 must keep track of resources it has already seen, then look those up when it hits a 208.
Examples
<response><href>/coll/dup</href><status>HTTP/1.1 208 Already Reported</status></response>Things that catch people out
- 208 carries no properties, so code that expects every response element to include a propstat block will throw on it.
- It is not an error and not a redirect. Treating it as either loses the resource from the enumeration.
Try it: HTTP Request Builder
Build a request with any method, headers and body, send it, and read the status line the server returns.
HTTP Request Builder
LOCAL · Browser-OnlyBuild and test HTTP requests with custom headers and body
Authentication
Headers
Generate Code
curl -X GET 'https://api.example.com/endpoint' \
-H 'Content-Type: application/json'Showing a sample URL. Enter your endpoint above to update the snippet.
Related HTTP status codes
All http status codes →207 Multi-Status
A WebDAV response carrying several independent status codes at once, one for each resource the request touched.
200 OK
The request succeeded. What the body contains depends on the method: a GET returns the resource, a POST returns the result of the action.
508 Loop Detected
The server aborted the operation because it detected an infinite loop while processing a request with WebDAV bindings.
226 IM Used
The server applied a delta encoding and is returning the difference from a version the client already has, rather than the whole resource.
300 Multiple Choices
The request matched more than one representation and the server is asking the client to pick, rather than choosing for it.
301 Moved Permanently
The resource has a new permanent URL, given in Location. Search engines transfer ranking signals to the target and clients may cache the redirect.
Tools for this
- HTTP Request Builder Free online HTTP request builder - build and test HTTP requests with custom headers and body
- HTTP Headers Checker Free online HTTP headers checker - view HTTP response headers for any URL