yahoo-eng-team team mailing list archive

[Samuel Lucidi <slucidi@xxxxxxxxxx>]

Public bug reported:

When using the Glance API's Content-Range support to partially download
an image, the server sets a Content-Length header equal to the size of
the full image, rather than the size of the chunk specified by the
Content-Range. This causes clients to wait indefinitely for the server.

Version-Release number of selected component (if applicable):
It at least affects Glance 11.0.1

Steps to Reproduce:
1. Make an authenticated GET request to /v2/images/<some_image_id>/file with
   the Content-Range header set to some value smaller than the entire length
   of the image.
2. Wait

Actual results:
Server returns a Content-Length header equal to the length of the whole image but only transmitting the requested bytes. The client waits indefinitely for the server to continue sending.

Expected results:
Server returns a Content-Length header equal to the number of bytes in the chunk, so that the client can know to disconnect.

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1618928

Title:
  Glance Content-Range request returns incorrect Content-Length

Status in Glance:
  New

Bug description:
  When using the Glance API's Content-Range support to partially
  download an image, the server sets a Content-Length header equal to
  the size of the full image, rather than the size of the chunk
  specified by the Content-Range. This causes clients to wait
  indefinitely for the server.

  Version-Release number of selected component (if applicable):
  It at least affects Glance 11.0.1

  Steps to Reproduce:
  1. Make an authenticated GET request to /v2/images/<some_image_id>/file with
     the Content-Range header set to some value smaller than the entire length
     of the image.
  2. Wait

  Actual results:
  Server returns a Content-Length header equal to the length of the whole image but only transmitting the requested bytes. The client waits indefinitely for the server to continue sending.

  Expected results:
  Server returns a Content-Length header equal to the number of bytes in the chunk, so that the client can know to disconnect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1618928/+subscriptions