Skip to content

fix-http-typos #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix-http-typos #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions en-US/rest/04_protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,19 +10,19 @@ All protocol versions need to be supported by the server. If the server does not

:::

### HTTTP1.1
### HTTP1.1

HTTP1.1 is currently the most popular version of the HTTP protocol, with well-known features such as maintaining connections and chunk transmission. Currently, almost all HTTP frameworks support this version. We can check the protocol version used on the response label.

![](arts/protocol_02.png)

### HTTTP2
### HTTP2

HTTP2 is currently a very commonly used HTTP protocol version. Compared with HTTP/1.1, its features such as multiplexing and header compression have very obvious performance advantages, but not all HTTP frameworks support this version. If the server does not support the HTTP2 protocol version, it will be downgraded to the HTTP1.1 protocol version, and we can check the specific protocol version used on the response label.

![](arts/protocol_03.png)

### HTTTP3
### HTTP3

HTTP3 is developed from [QUIC](https://www.ietf.org/rfc/rfc9000.txt). Compared with HTTP2, its performance and security have been further improved, but unfortunately, most HTTP services None of the frameworks support this version. As a new protocol in the future, Reqable still gives enough support. If the server does not support the HTTP3 protocol version, it will be downgraded to the HTTP/1.1 protocol version, and we can check the specific protocol version used on the response label.

Expand Down
6 changes: 3 additions & 3 deletions zh-CN/rest/04_protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,19 +10,19 @@ Reqable支持三种HTTP协议：[HTTP1.1](https://www.ietf.org/rfc/rfc2616.txt)

:::

### HTTTP1.1
### HTTP1.1

HTTP1.1是目前最普及的HTTP协议版本，具有我们熟知的保持链接、chunk传输等特性，目前几乎所有的HTTP服务框架都支持此版本。我们可以在响应标签上查看具体使用的协议版本。

![](arts/protocol_02.png)

### HTTTP2
### HTTP2

HTTP2是目前非常常用的HTTP协议版本，相比于HTTP1.1，其多路复用、头部压缩等特性具有非常明显的性能优势，但不一定是所有的HTTP服务框架都支持这个版本。如果服务端不支持HTTP2协议版本，则会被降级到HTTP1.1协议版本，我们可以在响应标签上查看具体使用的协议版本。

![](arts/protocol_03.png)

### HTTTP3
### HTTP3

HTTP3是从[QUIC](https://www.ietf.org/rfc/rfc9000.txt)发展而来，相比于HTTP2，其性能和安全得到进一步的提升，但很遗憾，大多数的HTTP服务框架都不支持这个版本。作为未来的新协议，Reqable还是给予了足够的支持。如果服务端不支持HTTP3协议版本，则会被降级到HTTP1.1协议版本，我们可以在响应标签上查看具体使用的协议版本。

Expand Down