[Bug 1657567] Re: "Content-Range: */<file size>" on non-416 responses considered invalid

[Julian Andres Klode]

Fix committed:

https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=4759a70

commit 4759a702081297bde66982efed8b2b7fd39ca27c
Author: Julian Andres Klode <jak at debian.org>
Date:   Wed Jan 18 20:39:27 2017 +0100

    basehttp: Only read Content-Range on 416 and 206 responses

    This fixes issues with sourceforge where the redirector includes
    such a Content-Range in a 302 redirect. Since we do not really know
    what file is meant in a redirect, let's just ignore it for all
    responses other than 416 and 206.

    Maybe we should also get rid of the other errors, and just ignore
    the field in those cases as well?

    LP: #1657567


** Changed in: apt (Ubuntu)
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1657567

Title:
  "Content-Range: */<file size>" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  APT only allows Content-Range: */<filesize> to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+subscriptions