[Bug 1657567] Re: "Content-Range: */<file size>" on non-416 responses considered invalid
Launchpad Bug Tracker
1657567 at bugs.launchpad.net
Wed Jan 25 16:22:00 UTC 2017
This bug was fixed in the package apt - 1.4~beta4ubuntu1
---------------
apt (1.4~beta4ubuntu1) zesty; urgency=medium
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Workaround debian/copyright symlink
-- Julian Andres Klode <juliank at ubuntu.com> Wed, 25 Jan 2017 12:07:50
+0100
** Changed in: apt (Ubuntu)
Status: Fix Committed => Fix Released
--
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
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