HTTP

HTTP 100 Continue vs 426 Upgrade Required

HTTP 100 (Continue) is a 1xx Informational response, while 426 (Upgrade Required) 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, 426 means that the server refuses to perform the request using the current protocol but might after the client upgrades to a different protocol.

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 server refuses to perform the request using the current protocol but might after the client upgrades to a different protocol.

When You See It

When a server requires HTTPS or a newer protocol version.

How to Fix

Switch to the protocol specified in the Upgrade response header.

Key Differences

1.

100 is a 1xx Informational response, while 426 is a 4xx Client Error response.

2.

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.

3.

HTTP 426: The server refuses to perform the request using the current protocol but might after the client upgrades to a different protocol.

4.

You encounter 100 when when a client sends an Expect: 100-continue header, the server responds with 100 before the client sends the body.

5.

You encounter 426 when when a server requires HTTPS or a newer protocol version.

When to Use Which

For 100 (Continue): This is an interim response — no fix needed. The client should continue sending the request body. For 426 (Upgrade Required): Switch to the protocol specified in the Upgrade response header.

Learn More