HTTP 100 Continue vs 208 Already Reported
HTTP 100 (Continue) is a 1xx Informational response, while 208 (Already Reported) is a 2xx Success response. 100 indicates that the server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected. In contrast, 208 means that used inside a DAV: propstat response element to avoid enumerating internal members of multiple bindings to the same collection repeatedly.
Description
The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
When You See It
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
How to Fix
This is an interim response — no fix needed. The client should continue sending the request body.
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.
Key Differences
100 is a 1xx Informational response, while 208 is a 2xx Success response.
HTTP 100: The server has received the request headers and the client should proceed to send the request body. This lets the client know it can continue with the request or abort if the headers were rejected.
HTTP 208: Used inside a DAV: propstat response element to avoid enumerating internal members of multiple bindings to the same collection repeatedly.
You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
You encounter 208 when in WebDAV responses to avoid duplicate listings.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 208 (Already Reported): No fix needed. This prevents redundant data in multi-status responses.