HTTP 100 Continue vs 302 Found
HTTP 100 (Continue) is a 1xx Informational response, while 302 (Found) is a 3xx Redirection 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, 302 means that the resource temporarily resides at a different URL. The client should continue using the original URL for future requests.
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
The resource temporarily resides at a different URL. The client should continue using the original URL for future requests.
When You See It
During A/B testing, temporary maintenance pages, or geo-based redirects.
How to Fix
Follow the Location header. Note: browsers may change POST to GET on redirect.
Key Differences
100 is a 1xx Informational response, while 302 is a 3xx Redirection 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 302: The resource temporarily resides at a different URL. The client should continue using the original URL for future requests.
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 302 when during A/B testing, temporary maintenance pages, or geo-based redirects.
When to Use Which
For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 302 (Found): Follow the Location header. Note: browsers may change POST to GET on redirect.