HTTP 100 Continue vs 413 Content Too Large
HTTP 100 (Continue) is a 1xx Informational response, while 413 (Content Too Large) is a 4xx Client Error 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, 413 means that the request payload exceeds the server's size limit.
Beschreibung
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.
Wann Sie es sehen
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
Wie man es behebt
This is an interim response — no fix needed. The client should continue sending the request body.
Beschreibung
The request payload exceeds the server's size limit.
Wann Sie es sehen
When uploading files that exceed the server's maximum upload size.
Wie man es behebt
Reduce the payload size. Check server limits (Nginx: client_max_body_size, Apache: LimitRequestBody).
Wesentliche Unterschiede
100 is a 1xx Informational response, while 413 is a 4xx Client Error 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 413: The request payload exceeds the server's size limit.
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 413 when when uploading files that exceed the server's maximum upload size.
Wann welchen verwenden
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 413 (Content Too Large): Reduce the payload size. Check server limits (Nginx: client_max_body_size, Apache: LimitRequestBody).