大网数据广告活动
Web 标准与前端开发

Upgrade header

· 52CE 我爱测

The HTTP **`Upgrade`** request header and response header can be used to upgrade an already-established client/server connection to a different protocol (over the same transport protocol). For example, it can be used by a client to upgrade a connection from HTTP/1.1 to HTTP/2, or

The HTTP Upgrade request header and response header can be used to upgrade an already-established client/server connection to a different protocol (over the same transport protocol). For example, it can be used by a client to upgrade a connection from HTTP/1.1 to HTTP/2, or an HTTP(S) connection to a WebSocket connection.

[!WARNING] HTTP/2 explicitly disallows the use of this mechanism and header; it is specific to HTTP/1.1.

<table class="properties"> <tbody> <tr> <th scope="row">Header type</th> <td> Request header, Response header </td> </tr> <tr> <th scope="row">Forbidden request header</th> <td>Yes</td> </tr> </tbody> </table>

Syntax

Upgrade: <protocol>[/<protocol_version>]
Upgrade: <protocol>[/<protocol_version>], …, <protocolN>[/<protocol_versionN>]

Directives

  • <protocol>
    • : Protocols are listed, comma-separated, in order of descending preference.
  • <protocol_version>
    • : An optional protocol version may be provided prefixed with a / forward slash.

Description

The Upgrade header field may be used by clients to invite a server to switch to one (or more) of the listed protocols, in descending preference order. For example, the client might send a GET request as shown, listing the preferred protocols to switch to (in this case example/1 and foo/2):

GET /index.html HTTP/1.1
Host: www.example.com
Connection: upgrade
Upgrade: example/1, foo/2

[!NOTE] The Connection header with type upgrade must always be sent with the Upgrade header.

The server can ignore the request, for any reason, in which case it should respond as though the Upgrade header had not been sent (for example, with a ). If the server will upgrade the connection, it must:

  1. Send back a response status with an Upgrade header that specifies the protocol(s) being switched to. For example:

    HTTP/1.1 101 Switching Protocols
    Upgrade: foo/2
    Connection: Upgrade
    
  2. Send a response to the original request using the new protocol (the server may only switch to a protocol with which it can complete the original request).

A server may also send the header as part of a 426 Upgrade Required response, to indicate that the server won't perform the request using the current protocol, but might do so if the protocol is changed. The client can then request a protocol change using the process above.

More detail and examples are provided in the topic Protocol upgrade mechanism.

Examples

Upgrade header with multiple protocols

The following request lists multiple protocols in descending preference:

Connection: upgrade
Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11

Upgrading to WebSocket

This is a common combination of headers to use to begin upgrading an HTTP connection to WebSockets. See Upgrading to a WebSocket connection for more information.

Connection: Upgrade
Upgrade: websocket

Specifications

Browser compatibility

See also

来源:MDN Web Docs / Mozilla 贡献者 · 作者与贡献记录 · CC BY-SA 2.5。离线整理了版式、链接和媒体显示。

资料来源与适用范围

资料来源
MDN Web Docs / Mozilla 贡献者
适用范围
请按文中版本与环境说明核对
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 2.5

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。