Comment 9 for bug 1655431

That does not really matter if it was there before or not. The problem is that there is now a redirect. That apparently was not there before.

In any case, this might take months to resolve for xenial - I have continously pushed updates for the past 2 months, but none of them has been accepted yet (one has finally been approved for -proposed, but that was two weeks ago already).

The other thing about the content range is a separate issues. The servers respond with
 "Content-Range: bytes */198384" on the 302 redirect. Which makes no real sense, but oh well.