{"id":36821,"date":"2025-06-03T09:35:55","date_gmt":"2025-06-03T09:35:55","guid":{"rendered":"https:\/\/www.resellerclub.com\/blog\/?p=36821"},"modified":"2025-07-07T13:14:49","modified_gmt":"2025-07-07T13:14:49","slug":"what-is-status-code-101","status":"publish","type":"post","link":"https:\/\/www.resellerclub.com\/blog\/what-is-status-code-101\/","title":{"rendered":"What is status code 101?"},"content":{"rendered":"

<\/p>\n

Status code 101 (also known as “101 Switching Protocols”) is an informational HTTP response code that indicates that the server is willing to switch protocols as requested by the client. <\/p>\n

<\/p>\n

<\/p>\n

When a client sends a request with an Upgrade header, the HTTP 1.1 101 Switching Protocols response confirms that the server will change to a different protocol for the remainder of the connection. This 101 status code is commonly used in scenarios like upgrading from HTTP to WebSocket connections or switching to newer versions of the HTTP protocol.<\/p>\n

<\/p>\n

<\/p>\n

What Causes the Status Code 101?<\/h2>\n

<\/p>\n

<\/p>\n

The 101 response code occurs when a client includes specific headers in their request indicating they want to change protocols. The essential requirements that trigger a status code 101 Switching Protocols are:<\/p>\n

<\/p>\n

<\/p>\n

    \n
  1. The client must include an “Upgrade” header specifying the desired protocol<\/li>\n
  2. A “Connection: Upgrade” header must be present in the request<\/li>\n
  3. The server must support and agree to use the requested protocol<\/li>\n<\/ol>\n

    <\/p>\n

    <\/p>\n

    The server will only send a 101 switching protocol response when changing protocols would be beneficial, such as switching to WebSocket for real-time communication or upgrading to a newer HTTP version. If the server doesn’t support or agree to the protocol change, it will respond with a different status code instead of the HTTP code 101.<\/p>\n

    <\/p>\n

    <\/p>\n

    Example<\/h2>\n

    <\/p>\n

    <\/p>\n

    Request:<\/strong><\/p>\n

    <\/p>\n

    <\/p>\n

    GET \/chat HTTP\/2.0\n\nHost: example101.com\n\nConnection: Upgrade\n\nUpgrade: websocket<\/code><\/pre>\n
    <\/p>\n
    <\/p>\n
    Response:<\/strong><\/p>\n
    <\/p>\n
    <\/p>\n
    HTTP\/2.0 101 Switching Protocols\n\nUpgrade: websocket\n\nConnection: Upgrade<\/code><\/pre>\n
    <\/p>\n
    <\/p>\n
    In this example, the client initiates a request to upgrade from regular HTTP to the WebSocket protocol for a chat application. The server responds with status code 101 switching protocols, confirming it will switch to the WebSocket protocol. <\/p>\n
    <\/p>\n
    <\/p>\n
    After this exchange, both client and server continue their communication using the WebSocket protocol instead of standard HTTP. This enables features like real-time bidirectional communication that are not possible with regular HTTP requests.<\/p>\n
    <\/p>\n
    <\/p>\n
    Reseller Club Hosting Services<\/h2>\n
    <\/p>\n
    <\/p>\n
    Reseller Hosting<\/a> | Windows Reseller Hosting<\/a> | Cloud Hosting<\/a> | VPS Hosting<\/a> | Managed VPS Hosting<\/a> | Dedicated Server Hosting<\/a> | Windows Dedicated Server<\/a> | Managed Dedicated Server<\/a> | Linux Shared Hosting<\/a> | Windows Shared Hosting<\/a><\/p>\n
    <\/p>\n
    \n\t\t\t  
    \n\t\t\t  <\/div><\/div>\n\t\t