Don't use cached items if --no-cache is specified and proxy is used

Currently apk would use cached in proxy copy of item it is fetching from repository because it does not indicate that it would prefer to use newest version. It would be useful if when —no-cache or other new option is used, apk would add “Cache-Control” HTTP header with value “no-cache” to ensure that newest copy of index and/or package is being downloaded.

(from redmine: issue id 8161, created on 2017-11-16, closed on 2019-05-03)

• Relations:
  • relates #5980 (closed)
• Changesets:
  • Revision f90af35e by Timo Teräs on 2018-01-03T12:25:07Z:

libfetch: add option to set "Cache-Control: no-cache"

ref #8161

• Revision 2da67940 by Timo Teräs on 2018-01-03T14:00:38Z:

url: add "Cache-Control: no-cache" header with --force-refresh

fixes #8161

• Revision b7f70c06 by Timo Teräs on 2018-01-09T07:56:05Z:

libfetch: add option to set "Cache-Control: no-cache"

ref #8161

(cherry picked from commit f90af35e9c563bd4f865d8d47a7ae357191494db)

• Revision ecc6d60e by Timo Teräs on 2018-01-09T07:56:15Z:

url: add "Cache-Control: no-cache" header with --force-refresh

fixes #8161

(cherry picked from commit 2da67940d50865d206f6a79165ce7b3de5a90de3)

added Closed Feature Normal labels

I have a patch for this. But just before pushing it occurred to me that `—no-cache` is often used in docker installs and similar to not make a local cache of packages. I wonder if this would deserve a different option. Thoughts?

(from redmine: written on 2018-01-03)

Maybe —force-http-refresh or similar?

(from redmine: written on 2018-01-03)

Applied in changeset commit:2da67940.

(from redmine: written on 2018-01-03)

closed

mentioned in commit b7f70c06

mentioned in commit ecc6d60e

mentioned in commit f90af35e