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

Łukasz Zemczak 1657567 at bugs.launchpad.net
Thu Mar 2 13:19:12 UTC 2017


Since this (and a few other) bug is mentioned in the SRU changelog,
please update the description to include the SRU template. There seems
to be a master bug for the SRU, but each bug should *at least* have a
clearly written test-case. Thanks!

-- 
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:
  In Progress
Status in apt source package in Yakkety:
  In Progress

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