3 ms·
The difficulty is if the mirror itself is behind, Cloudflare's cache for that specific endpoint will be correct (functional, working) but out of date compared t
by gravitas 6y ago
The difficulty is if the mirror itself is behind, Cloudflare's cache for that specific endpoint will be correct (functional, working) but out of date compared to another mirror.
Example: around the end of June this year the mirrors.kernel.org infra was failing to sync (DNS issues of some sort) the latest content, so your upgrade would appear to have no new packages because the stale content was a valid repo, when in fact there were many updates and other mirrors were in sync.
- iforgotpassword 6y agoRight that makes sense, so Cloudflare would actually have to make the caching context-aware, not just classic HTTP proxying.
- gravitas 6y agoI'm not aware of the technical how, but the Arch infrastructure seems to measure this successfully; a hook into this data might be a great way for the two to interoperate (so that Cloudflare always serves the freshest cache/mirrors). https://www.archlinux.org/mirrors/status/ https://www.archlinux.org/mirrors/status/
- Foxboron 6y agoThe relevant code can be found here I believe: https://github.com/archlinux/archweb/blob/master/mirrors/management/commands/mirrorcheck.py https://github.com/archlinux/archweb/blob/master/mirrors/man...