HTTP 100 Continue vs 200 OK
HTTP 100 (Continue) is a 1xx Informational response, while 200 (OK) 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, 200 means that the request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
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 request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
Cuándo lo verás
The most common HTTP response — indicates the request was processed successfully.
Cómo solucionarlo
No fix needed. The request succeeded as expected.
Diferencias clave
100 is a 1xx Informational response, while 200 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 200: The request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
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 200 when the most common HTTP response — indicates the request was processed successfully.
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 200 (OK): No fix needed. The request succeeded as expected.