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

[Julian Andres Klode]

Seems like sourceforge is fixed now, so we need to come up with a new
test.

** Description changed:

  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]
+ TODO.
+ 
+ [Regression Potential] 
+ None

-- 
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.

  
  [Impact] 
  Issue breaks and other services that respond with a Content-Range header in a 302 redirect, or any non 416 one.

  [Test Case]
  TODO.

  [Regression Potential] 
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+subscriptions