Pages that are only in common, always force an https connection

common vs specific platform

Take for example the command: tldr tldr on linux (Let's assume I already have the file common/tldr.md in my cache directory and it is newer than TLDR_CACHE_MAX_AGE).

One might reasonably assume that no https requests will be made. But in fact, the program first looks for linux/tldr.md, since it's not in the cache, it first requests it from
PAGES_SOURCE_LOCATION/linux/tldr.md
which returns a 404. then after all this, it looks for common/tldr.md and shows the contents.

Solution

I suggest checking the common cache directory before making an https connection for platform specific files. Or to avoid changing default behavior, at least put this behavior behind an option like
--common-before-net

Start with the tldr tldr command flow on Linux and trace how the cache is checked before requests to PAGES_SOURCE_LOCATION/linux/tldr.md. Verify the existing common/tldr.md cache case described in the issue. Done means a fresh common cached page is shown without an HTTPS request for the platform-specific page, while the existing behavior remains defined for other cases.