101 Switching Protocols
1xx informational
Server agrees to switch protocols as requested by the client via the Upgrade header, typically moving from HTTP to WebSocket on the same connection.
Common causes
- The page opens a WebSocket connection with an Upgrade: websocket handshake.
- A client attempts an h2c upgrade from plain HTTP on port 80.
- An application requests a protocol switch that the origin actually supports.
How to fix it
- Confirm Upgrade and Connection headers reach the backend through every proxy.
- Enable WebSocket support in the reverse proxy and terminate TLS with wss in production.
- Avoid h2c upgrades unless the whole path supports them, and fall back cleanly when it does not.
What it means for redirects and SEO
Crawlers pass over an upgraded connection, but a 101 returned to a plain HTML fetch signals a misconfiguration. Link checkers often flag it because there is no document body. Keep the upgrade endpoint separate from crawlable URLs.