tool::http-status-detail

101 Switching Protocols

Server is switching protocols as requested.

Status Code

101

Name

Switching Protocols

Detailed Explanation

HTTP 101 Switching Protocols indicates the server is switching to the protocol specified in the client's Upgrade header. The most common use case is upgrading an HTTP connection to WebSocket. After this response, the connection uses the new protocol. It is a critical step in the WebSocket handshake.

Common Causes

▸A WebSocket handshake request (Upgrade: websocket header)
▸A request to upgrade from HTTP/1.1 to HTTP/2 (h2c)
▸Any client request that includes an Upgrade header for protocol switching

How to Fix

1.101 is a normal protocol switching response — no fix needed
2.Specify the desired protocol in the Upgrade header (e.g., websocket, h2c)
3.Verify the server supports the requested protocol before upgrading

Related HTTP Headers

UpgradeConnection

Response Example

HTTP/1.1 101 Switching Protocols
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=

Related Status Codes

100ContinueClient should continue with the request.→102ProcessingServer has received the request but has not yet completed it.→103Early HintsUsed to preload resources while the server is still processing.→

← Back to all status codes

// related tools

⏱

Cron Expression Generator

Build and parse cron expressions visually. Generate human-readable descriptions and preview next execution times.

jwt

JWT Decoder

Decode and inspect JWT tokens. View header, payload, and signature details.

Regex Tester

Test regular expressions with live matching, group highlighting, and explanations.

◑

Color Converter

Convert colors between HEX, RGB, HSL, and more. Pick colors visually.