208 Already Reported

What HTTP 208 Already Reported Means

The members of a WebDAV binding have already been enumerated and are not repeated.

Used inside a 207 Multi-Status response to avoid listing the same resource multiple times.

Common Causes

• WebDAV bindings referenced more than once
• Avoiding duplicate enumeration in a Multi-Status response

How to Fix It (For Visitors)

• No action needed

How to Fix It (For Developers/Admins)

• Use 208 within a 207 response to suppress duplicates
• Track already-reported bindings server-side

Returning a 208 Already Reported (Code Examples)

If you build APIs or web apps, here is how to send an HTTP 208 response and how to test for it:

Node.js (Express)

app.get('/resource', (req, res) => {
  res.status(208).json({ error: 'Already Reported' });
});

Python (Flask)

@app.route('/resource')
def resource():
    return jsonify(error='Already Reported'), 208

PHP

<?php
http_response_code(208);
header('Content-Type: application/json');
echo json_encode(['error' => 'Already Reported']);

Check the status with curl

curl -I https://example.com/resource
# Look for: HTTP/1.1 208 Already Reported

Frequently Asked Questions

What does HTTP 208 Already Reported mean?

Used inside a 207 Multi-Status response to avoid listing the same resource multiple times. In short: The members of a WebDAV binding have already been enumerated and are not repeated.

How should I handle an HTTP 208 Already Reported response?

Use 208 within a 207 response to suppress duplicates. Track already-reported bindings server-side.

Official Specification

The 208 Already Reported status code is defined in RFC 5842 Section 7.1.

View the IANA HTTP Status Code Registry →