[Bug 1657567] Re: "Content-Range: */<file size>" on non-416 responses considered invalid
Jon Grimm
jon.grimm at canonical.com
Mon Mar 27 15:09:53 UTC 2017
** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-needed-yakkety
--
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:
Fix Committed
Status in apt source package in Yakkety:
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.
[Impact]
Issue breaks and other services that respond with a Content-Range header in a 302 redirect, or any non 416 one.
[Test Case]
Run
/usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
http://www.jak-software.de/lp1657567 ubuntu.iso
Before:
E: Failed to fetch http://www.jak-software.de/lp1657567 The HTTP
server sent an invalid Content-Range header Bad header data
After:
Redirect is followed successfully and a zesty live image is being
downloaded.
[Regression Potential]
None
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