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

Julian Andres Klode julian.klode at gmail.com
Wed Feb 22 17:08:26 UTC 2017


Queued for 1.2.20:

  https://github.com/Debian/apt/compare/1.2.19...julian-
klode:1.2.y?expand=1

Queued for 1.3.5:

  https://github.com/Debian/apt/compare/1.3.4...julian-
klode:1.3.y?expand=1


** Also affects: apt (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: apt (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: apt (Ubuntu Yakkety)
       Status: New => Triaged

-- 
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 Released
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged

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



More information about the foundations-bugs mailing list