IssueRaiser

Add HTTP/2 Support in Proxy Layer

The proxy layer currently doesn't really support HTTP/2. The only case in which a user can take advantage of HTTP/2 is if they are making a non-intercepted request through the `https-proxy`, and when #687 lands, all requests will be intercepted. When a request is intercepted, it can't be upgraded to HTTP/2. Take this page, which loads 1000 images: https://flotwig.github.io/cypress-fetch-page/index1000.html Loaded with HTTP/2, 1000 images load in 1362ms on my browser. With HTTP/1.1, it takes 3896ms - three times as long. Making our backend requests use HTTP/2 would give us a huge performance boost for making requests against servers that support it. Obstacles: 1. `request` library doesn't support HTTP/2 - we'd need to fork or figure out a different way to try to upgrade to `http2` 2. need to figure out how HTTP/2 interacts with HTTP proxies

Posted by flotwig on Mar 14, 2019, 2:19 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

support (Software)

Add HTTP/2 Support in Proxy Layer

flotwigMar 14, 2019, 2:19 PM

The proxy layer currently doesn't really support HTTP/2. The only case in which a user can take advantage of HTTP/2 is if they are making a non-intercepted request through the `https-proxy`, and when #687 lands, all requests will be intercepted. When a request is intercepted, it can't be upgraded to HTTP/2. Take this page, which loads 1000 images: https://flotwig.github.io/cypress-fetch-page/index1000.html Loaded with HTTP/2, 1000 images load in 1362ms on my browser. With HTTP/1.1, it takes 3896ms - three times as long. Making our backend requests use HTTP/2 would give us a huge performance boost for making requests against servers that support it. Obstacles: 1. `request` library doesn't support HTTP/2 - we'd need to fork or figure out a different way to try to upgrade to `http2` 2. need to figure out how HTTP/2 interacts with HTTP proxies

Comments (0)

No comments yet. Start the discussion.

Comment on this issue