HTTP 100 Continue vs 102 Processing
Both HTTP 100 (Continue) and 102 (Processing) belong to the 1xx Informational category. 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. Meanwhile, 102 means that the server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
Descrição
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.
Quando você o vê
When a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.
Como corrigir
This is an interim response — no fix needed. The client should continue sending the request body.
Descrição
The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
Quando você o vê
During long-running WebDAV operations.
Como corrigir
Wait for the final response. This is an interim status to prevent timeouts.
Diferenças principais
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 102: The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
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 102 when during long-running WebDAV operations.
Quando usar qual
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts.