CARVIEW

MOTORHOMES

Select Language

HTTP/2 301 content-security-policy: script-src 'sha256-1az3CiAdXAaMP3TFl5msfrDjNuSHMdg1ecAgxfZPR50=' 'unsafe-inline' 'strict-dynamic'; object-src 'none'; base-uri 'none'; report-uri https://csp.withgoogle.com/csp/chromium-website/ location: https://www.chromium.org/developers/design-documents/network-stack/http-pipelining content-type: text/plain; charset=utf-8 accept-ranges: bytes date: Mon, 13 Oct 2025 10:34:49 GMT x-served-by: cache-bom-vanm7210056-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1760351689.949909,VS0,VE124 vary: x-fh-requested-host, accept-encoding alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 content-length: 97 HTTP/2 301 content-security-policy: script-src 'sha256-1az3CiAdXAaMP3TFl5msfrDjNuSHMdg1ecAgxfZPR50=' 'unsafe-inline' 'strict-dynamic'; object-src 'none'; base-uri 'none'; report-uri https://csp.withgoogle.com/csp/chromium-website/ location: /developers/design-documents/network-stack/http-pipelining/ content-type: text/plain; charset=utf-8 accept-ranges: bytes date: Mon, 13 Oct 2025 10:34:49 GMT x-served-by: cache-bom-vanm7210078-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1760351689.127912,VS0,VE123 vary: x-fh-requested-host, accept-encoding alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 content-length: 74 HTTP/2 200 cache-control: max-age=3600 content-encoding: gzip content-security-policy: script-src 'sha256-1az3CiAdXAaMP3TFl5msfrDjNuSHMdg1ecAgxfZPR50=' 'unsafe-inline' 'strict-dynamic'; object-src 'none'; base-uri 'none'; report-uri https://csp.withgoogle.com/csp/chromium-website/ content-type: text/html; charset=utf-8 etag: "8124dbdf911ae9cb903f5c38ac8884b92052459ef015c01d3878656baaa04afa" last-modified: Fri, 10 Oct 2025 02:31:02 GMT strict-transport-security: max-age=31556926 accept-ranges: bytes date: Mon, 13 Oct 2025 10:34:49 GMT x-served-by: cache-bom-vanm7210078-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1760351689.264489,VS0,VE210 vary: x-fh-requested-host, accept-encoding alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 content-length: 2353 HTTP Pipelining

The Chromium Projects

For Developers > Design Documents > Network Stack >

HTTP Pipelining

Objective

Speed up Chrome's network stack by enabling HTTP Pipelining. Pipelining issues multiple requests over a single connection without waiting for a response.

Risks

Broken servers. Servers may ignore pipelined requests or corrupt the responses.
Broken proxies. May cause the same problems. Some users are behind "transparent proxies," where the requests are proxied even though the user has not explicitly specified a proxy in their system configuration.
Front of queue blocking. The first request in a pipeline may block other requests in the pipeline. The net result of pipelining may be slower page loads.

Mitigation

Response headers must have the following properties:

HTTP/1.1
Determinable content length, either through explicit Content-Length or chunked encoding
A keep-alive connection (implicit with HTTP/1.1)
No authentication

Pipelining does not begin until these criteria have been met for an origin (host and port pair). If at any point one of these fail, the origin is black-listed in the client. If an origin has successfully pipelined before, it is remembered and pipelining begins immediately on next use.

Status

The option to enable pipelining has been removed from Chrome, as there are known crashing bugs and known front-of-queue blocking issues. There are also a large number of servers and middleboxes that behave badly and inconsistently when pipelining is enabled. Until these are resolved, it's recommended nobody uses pipelining. Doing so currently requires a custom build of Chromium.

Original Source | Taken Source