3 ms·
> Unless you control the TLS terminators Nope, this is all about trusting vendors. Unless you're building your own computer chips and laying your own fiber, yo
by manigandham 10y ago
> Unless you control the TLS terminators
Nope, this is all about trusting vendors. Unless you're building your own computer chips and laying your own fiber, you're just blaming a vendor for what seems like personal issues.
> problem is generally not in the network latency
Again years of research has shown this is one of the biggest issues on the web. Read https://www.igvita.com/ https://www.igvita.com/ for some good info.
> Yes, both technically use reverse proxying technology in their stack, but in the end they are completely different approaches.
Nope, this clearly shows you don't have any understanding. CF is a CDN. That's it. Instead of like other CDNs that offer a CNAME that you point your DNS to, they just offer a free DNS service that automates the CNAME entry into a single button.
All CDNs today are reverse proxies that will either return a cached response or proxy the request to the origin if the cache is empty. You can also use every CDN to proxy dynamic requests and many do. And yes, there are a few that offer a push model where you upload assets explicitly but this is the exception, not the standard.
You're talking about CF as if they're something unique when they do exactly the same thing as everyone else. Use them on a subdomain if you want and leave the main domain unproxied, use them only for static files or for dynamic requests, use them to proxy everything or cache everything including HTML. It's all just configuration. Why is this such a problem for you?