HTTP/1.1
Version 1.1 of the HTTP protocol, which introduced mechanisms such as persistent connections (keep-alive) and chunked transfer encoding. It is a widely used protocol version in web services.
Timeline (last 90 days)
Compared with HTTP/1.1, HTTP/2 introduces binary framing, header compression and multiplexing.
GZip compression support was first introduced as early as 1997 by the HTTP/1.1 specification (RFC 2068).
Age is an HTTP/1.1 response header describing how long a cached response has been stored, in seconds, added or updated by the cache server on a cache hit, representing the time elapsed since the response was generated or validated by the caching node.
HTTP/1.1's Transfer-Encoding: chunked allows the server to send data in chunks without knowing the final content length, but the RFC specification does not prohibit proxies from reordering, merging or buffering chunks.
SSE runs on top of standard HTTP/1.1 chunked transfer encoding or HTTP/2 and HTTP/3 multiplexed streams.
HTTP/1.1 connection reuse determination involves dimensions such as whether the response carries Content-Length or uses Transfer-Encoding: chunked, whether the status code is 204/304, and whether the request method is CONNECT or Upgrade.
In HTTP/1.1, connections are persistent by default, and unless the response explicitly carries Connection: close, the client should consider the connection still reusable.
The HTTP Range request mechanism was introduced by HTTP/1.1, allowing clients to fetch only a certain byte range of a resource via the Range request header.
The HTTP/1.1 specification (RFC 7230) stipulates that request header field names are case-insensitive.
HTTPX supports the HTTP/2 protocol, whereas requests only supports HTTP/1.1.
1 more timeline events
All Facts (13)
HTTP 402（Payment Required）是HTTP/1.1规范中最早定义的状态码之一，长期处于保留状态
90%UnverifiedCompared to HTTP/1.1, HTTP/2 supports multiplexing, header compression, and server push, resolving the head-of-line blocking problem of HTTP/1.1.
65%UnverifiedRoy Fielding is one of the principal designers of the HTTP/1.1 protocol.
60%UnverifiedCompared with HTTP/1.1, HTTP/2 introduces binary framing, header compression and multiplexing.
50%UnverifiedGZip compression support was first introduced as early as 1997 by the HTTP/1.1 specification (RFC 2068).
50%UnverifiedAge is an HTTP/1.1 response header describing how long a cached response has been stored, in seconds, added or updated by the cache server on a cache hit, representing the time elapsed since the response was generated or validated by the caching node.
50%UnverifiedHTTP/1.1's Transfer-Encoding: chunked allows the server to send data in chunks without knowing the final content length, but the RFC specification does not prohibit proxies from reordering, merging or buffering chunks.
50%UnverifiedSSE runs on top of standard HTTP/1.1 chunked transfer encoding or HTTP/2 and HTTP/3 multiplexed streams.
50%UnverifiedHTTP/1.1 connection reuse determination involves dimensions such as whether the response carries Content-Length or uses Transfer-Encoding: chunked, whether the status code is 204/304, and whether the request method is CONNECT or Upgrade.
50%UnverifiedIn HTTP/1.1, connections are persistent by default, and unless the response explicitly carries Connection: close, the client should consider the connection still reusable.
50%UnverifiedThe HTTP Range request mechanism was introduced by HTTP/1.1, allowing clients to fetch only a certain byte range of a resource via the Range request header.
50%UnverifiedThe HTTP/1.1 specification (RFC 7230) stipulates that request header field names are case-insensitive.
50%UnverifiedHTTPX supports the HTTP/2 protocol, whereas requests only supports HTTP/1.1.
50%