Public bug reported:
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.
** Affects: apt (Ubuntu)
Importance: Low
Status: Triaged
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
