HTTP 101 Switching Protocols vs 200 OK
HTTP 101 (Switching Protocols) is a 1xx Informational response, while 200 (OK) is a 2xx Success response. 101 indicates that the server understands the Upgrade header field request and indicates which protocol it is switching to. 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.
Description
The server understands the Upgrade header field request and indicates which protocol it is switching to.
When You See It
When upgrading from HTTP/1.1 to WebSocket, or to HTTP/2.
How to Fix
This is normal behavior during protocol upgrades. Ensure your client supports the target protocol.
Description
The request succeeded. The meaning depends on the HTTP method: GET returns the resource, POST reports the action result, HEAD returns headers only.
When You See It
The most common HTTP response — indicates the request was processed successfully.
How to Fix
No fix needed. The request succeeded as expected.
Key Differences
101 is a 1xx Informational response, while 200 is a 2xx Success response.
HTTP 101: The server understands the Upgrade header field request and indicates which protocol it is switching to.
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 101 when when upgrading from HTTP/1.1 to WebSocket, or to HTTP/2.
You encounter 200 when the most common HTTP response — indicates the request was processed successfully.
When to Use Which
For 101 (Switching Protocols): This is normal behavior during protocol upgrades. Ensure your client supports the target protocol. For 200 (OK): No fix needed. The request succeeded as expected.