On Tue, 2019-06-04 at 18:54 -0700, Samuel Sieb wrote:
On 6/1/19 5:27 AM, Garry T. Williams wrote:
On Friday, May 31, 2019 11:05:20 PM EDT Tim via users wrote:
On Fri, 2019-05-31 at 17:18 -0400, Garry Williams wrote:
But, of course, the issue is why this happens in the first place.
Does your ISP insert a transparent proxy between you and the internet? They're well known to cause caching problems.
Ah, ha! That is a difference between the problem system and the others I have that do not experience the problem.
My employer does eavesdrop on everything.
I think I found the answer to this. I ran into the same problem with my simple custom proxy. Starting in F30, the repo uses zchunk. This means that dnf requests lots of byte ranges. If the proxy doesn't support this, then librepo fails. According to the http specs, a client MUST support getting more (or less) data than asked for when requesting ranges. However, librepo does not. I'm about to file a bug for this.
Please do, and please file it against zchunk when you do, but please first make sure you've updated to the latest versions if libdnf, librepo and zchunk-libs. librepo is supposed to automatically reduce the number of zchunk byte ranges it requests if there's a failure, so, if it's not, it's most likely a bug.
It would also be really helpful to see how your proxy responds to a request for too many byte ranges. And please make sure to attach dnf.librepo.log when you file the bug.
Jonathan