HTTP 100 Continue vs 400 Bad Request
HTTP 100 (Continue) is a 1xx Informational response, while 400 (Bad Request) 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, 400 means that the server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
Descripción
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.
Cuándo lo verás
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
Cómo solucionarlo
This is an interim response — no fix needed. The client should continue sending the request body.
Descripción
The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
Cuándo lo verás
When sending malformed JSON, missing required fields, or invalid query parameters.
Cómo solucionarlo
Check the request body format, validate all required fields, and ensure proper encoding.
Diferencias clave
100 is a 1xx Informational response, while 400 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 400: The server cannot process the request due to malformed syntax, invalid request message framing, or deceptive request routing.
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 400 when when sending malformed JSON, missing required fields, or invalid query parameters.
Cuándo usar cada uno
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 400 (Bad Request): Check the request body format, validate all required fields, and ensure proper encoding.