4 ms·

Quick question, if I have a VPS with cloudflare in front of it where the VPS runs a HTTP1.1 server is cloudflare limited to 6 http connections/resources to my s

Quick question, if I have a VPS with cloudflare in front of it where the VPS runs a HTTP1.1 server is cloudflare limited to 6 http connections/resources to my server at a time?

CasperDern 5y ago
I do not know about cloudflare's internals, but I believe the 6 connections limit is purely a browser thing. So it should be able to do as many connections as it's able to handle.
- bestinterest 5y ago
  Ah okay thats good news. Is it worth upgrading to HTTP2 on the server side for cloudflare if they are the only consumers of my VPS? They already enable HTTP/3 for clients but I'm wondering if I'm somehow bottlenecking them by not matching my server with HTTP/2 or HTTP/3.
  - johncolanduoni 5y ago
    According to their docs Cloudflare won’t connect to your origin servers with HTTP/2 or HTTP/3 anyway: https://support.cloudflare.com/hc/en-us/articles/200168076-Understanding-Cloudflare-HTTP-2-and-HTTP-3-Support https://support.cloudflare.com/hc/en-us/articles/200168076-U... In general connections between CDNs/reverse proxies and origin servers don’t get much benefit from HTTP/2 or HTTP/3. CDNs don’t generally care about connection establishment speed or multiplexing to the origin (the main benefits of newer HTTP versions), since they can just create and maintain N long-lived connections if they want to be able to send N concurrent requests. They generally only bother with HTTP/2 to the origin if they need to support gRPC, which has some unusual connection semantics.
slig 5y ago
If you configure your static files caching correctly, they will be served directly by Cloudflare in the fastest way possible given the user has a modern browser. You can use http://webpagetest.org/ http://webpagetest.org/ (or Chrome Dev Tools) and look for `cf-cache-status: HIT` header on the content that should be served directly by CF.

Quick question, if I have a VPS with cloudflare in front of it where the VPS runs a HTTP1.1 server is cloudflare limited to 6 http connections/resources to my server at a time?

CasperDern 5y ago

I do not know about cloudflare's internals, but I believe the 6 connections limit is purely a browser thing. So it should be able to do as many connections as it's able to handle.

bestinterest 5y ago
Ah okay thats good news. Is it worth upgrading to HTTP2 on the server side for cloudflare if they are the only consumers of my VPS? They already enable HTTP/3 for clients but I'm wondering if I'm somehow bottlenecking them by not matching my server with HTTP/2 or HTTP/3.
- johncolanduoni 5y ago
  According to their docs Cloudflare won’t connect to your origin servers with HTTP/2 or HTTP/3 anyway: https://support.cloudflare.com/hc/en-us/articles/200168076-Understanding-Cloudflare-HTTP-2-and-HTTP-3-Support https://support.cloudflare.com/hc/en-us/articles/200168076-U... In general connections between CDNs/reverse proxies and origin servers don’t get much benefit from HTTP/2 or HTTP/3. CDNs don’t generally care about connection establishment speed or multiplexing to the origin (the main benefits of newer HTTP versions), since they can just create and maintain N long-lived connections if they want to be able to send N concurrent requests. They generally only bother with HTTP/2 to the origin if they need to support gRPC, which has some unusual connection semantics.

slig 5y ago

If you configure your static files caching correctly, they will be served directly by Cloudflare in the fastest way possible given the user has a modern browser. You can use http://webpagetest.org/ http://webpagetest.org/ (or Chrome Dev Tools) and look for `cf-cache-status: HIT` header on the content that should be served directly by CF.