HTTP/2的哪些部分是有状态的? [英] Which parts of HTTP/2 are stateful?

问题描述

与原始的无状态HTTP/1不同， HTTP/2 具有许多有状态组件. /p>

HTTP/2的这些部分是有状态的:

• 标头块引用的是有状态的无符号31位整数，称为流标识符
• 框架还引用了相同的有状态流标识符
• 机会性加密也取决于状态，因为TLS是有状态的

HTTP/2的其他部分是否是有状态的?

解决方案

HTTP 2将许多有状态组件添加到HTTP语料库中.

• 流使用有状态的无符号31位整数，称为溪流 标识符".
• 标头块用于有状态地建立流标识符.
• 框架是有状态的.
• 标头压缩是有状态的.
• 机会主义加密是有状态的.

以下是从以前的HTTP附加内容中携带的有状态组件，这些组件在HTTP 2中仍然是有状态的.

• Cookie是有状态的.
• HTTPS是有状态的.
• HTTP缓存是有状态的. HTTP定义的身份验证是有状态的. Web套接字是有状态的，并使用有状态的"Sec-WebSocket" -密钥" HTTP标头.
• 网络存储(尽管不是HTTP)也是有状态的.

Unlike the original stateless HTTP/1, HTTP/2 has many stateful components.

These parts of HTTP/2 are stateful:

• Header blocks refer to a stateful unsigned 31-bit integer called a stream identifier
• Frames also reference the same stateful stream identifier
• opportunistic encryption also depends on state since TLS is stateful

Are there any other parts of HTTP/2 that are stateful?

解决方案

HTTP 2 adds many stateful components to the HTTP corpus.

• Streams use a stateful unsigned 31-bit integer called a "stream identifier".
• Header blocks are used to statefully establish the stream identifier.
• Frames are stateful.
• Header compression is stateful.
• Opportunistic encryption is stateful.

The following are stateful components carried from previous HTTP additions which are still stateful in HTTP 2.

• Cookies are stateful.
• HTTPS is stateful.
• HTTP caching is stateful. (See also RFC 7234.)
• HTTP defined authentication is stateful. (See also RFC 7235)
• Web Sockets are stateful and use a stateful "Sec-WebSocket-Key" HTTP header.
• Web Storage, although not HTTP, is also stateful.

这篇关于HTTP/2的哪些部分是有状态的?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！