Dear Maintainer,

* What led up to the situation?

Normal ACNG operation when the mirror uses 302 for file(s)

* What exactly did you do

Nothing was done by us to initiate the unwanted behaviour.  Aparently the
mirror and repo maintainers have started using 302s routinely.

No fix has been attempted

* What was the outcome of this action?

The outcome of ACNG's routine behaviour is that it sends an email every day like:

Subject: Cron: test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
Date: Fri, 21 Dec 2018 06:25:13 +0530 (IST)
From: "root@<redacted>" <<redacted>>
To: root@<redacted>

/etc/cron.daily/apt-cacher-ng:
Maintenance Task: Expiration
See file /var/log/apt-cacher-ng/maint_1545353701.log.html for more details.
Server control address: http://127.0.0.1:3142/acng-report.html
Errors found, aborting expiration...


These mails mean real defects requiring intervention are not fixed because it is
impracticable to run ACNG maintenance every day (normally we do so on receiving
such mails from ACNG).

ACNG successfuly downloads files after getting a 302; apparently it follows the
redirection.

* What outcome did you expect instead?

We expect to recieve such mails from ACNG only when it detects errors.