5 ms·
Why should you need to provision a CDN when If-Modified-Since / Etags exist? I get that not every client is well behaved, but you'd hope that Firefox would be,
by EdwardDiego 2y ago
Why should you need to provision a CDN when If-Modified-Since / Etags exist?
I get that not every client is well behaved, but you'd hope that Firefox would be, given Mozilla's presence in web standards.
(Which, tbh makes me think this issue is the "on iOS" bit, given it's Firefox. I presume Apple still has their "only Safari's rendering engine" rule in place for... ...reasons)
- yosefk 2y agoA CDN caches across users, lowers latency by having servers closer to the user, and lowers the bandwidth your server needs to handle. Cloudflare CDN has a free tier and I assume others do, too, so it's fairly easy to provision.
- mcculley 2y agoWhy would the issue be “on iOS”? The renderer has nothing to do with how pages are fetched.
- EdwardDiego 2y agoBecause Apple.
- jampekka 2y agoThey probably have to write a totally different fetching logic for the Safari wrapper. If Apple wasn't as scummy as they are, they would have used the same logic as in other platforms where this problem doesn't seem to exist.