Re:Cloudflare's new AI traffic options for customers
by dbbk on Saturday July 25, 2026 @10:30PM
(#49054072)
So you're against all CDNs?
[ Parent
| on HN ]
Re:Cloudflare's new AI traffic options for customers
by fc417fc802 on Saturday July 25, 2026 @10:39PM
(#49054131)
A CDN doesn't necessarily have to perform a MitM. We really need more nuanced terminology to distinguish the various approaches.
Re:Cloudflare's new AI traffic options for customers
by sandeepkd on Saturday July 25, 2026 @10:59PM
(#49054254)
Ideally yes, the TLS termination does not need to happen for caching purposes. Challenge is that in practice every business wants to be sticky and try to provide more functionalities which do require TLS termination. Most people either trust CDN's or they do not understand MitM so it does not concerns them. Plus they are getting certificate management and DDOS prevention capabilities.
Re:Cloudflare's new AI traffic options for customers
by inigyou on Monday July 27, 2026 @06:17AM
(#49067442)
How can you cache without terminating TLS? Remember, every TLS session uses different encryption keys, so encrypted responses cannot be cached.
Re:Cloudflare's new AI traffic options for customers
by gruez on Saturday July 25, 2026 @10:53PM
(#49054207)
Right, but practically speaking all CDNs are MITMs. If you're against cloudflare you should be against cloudfront, akamai, etc. as well.
Re:Cloudflare's new AI traffic options for customers
by inigyou on Sunday July 26, 2026 @05:12AM
(#49056166)
Cloudflare is egregiously bad because of its marketing strategy. It tried to get everyone with any small website to use it, by selling a vague notion of security and charging no monetary price, and it worked. They'll even sell you a domain name to increase lockin. Many people recommend getting domains from cloudflare because apparently they're cheap.
Akamai, Fastly, etc only take big customers who know what they're doing. You need to sign a proper contract with them. They aren't low-friction.