Accept Range requests and set appropriate response

Bug #1680310 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Undecided
Unassigned

Bug Description

https://review.openstack.org/441501
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/glance" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 423f3401741a64f0ead66bcb8cb0cd8cafb02cf8
Author: Dharini Chandrasekar <email address hidden>
Date: Fri Mar 3 22:38:34 2017 +0000

    Accept Range requests and set appropriate response

    Currently glance v2 API incorrectly accepts ‘Content-Range’ header
    for random image access and does not set response headers.
    As per rfc7233, ‘Range’ requests should be accepted and ‘Content-Range’
    must be returned in the response headers.

    This patch enables Glance v2 API to accept the more appropriate ‘Range’
    requests and sets ‘Content-Range’ response header.

    For backward compatibility with pre-Pike Glance clients, the incorrect
    'Content-Range' header will be accepted silently in perpetuity.
    Thus this patch contains tests for 'Content-Range' in requests to
    prevent regressions.

    DocImpact
    Implements lite-spec I5bdadde682a0c50836bd95e2a6651d6e7e18f172
    Closes-Bug: #1677391

    Co-Authored-By: Hemanth Makkapati <email address hidden>

    Change-Id: Ib7ebc792c32995751744be3f36cbc9a0c1eead2a

Tags: doc glance
Revision history for this message
Brian Rosmaita (brian-rosmaita) wrote :

This was addressed by Change-Id: I70e3f60c3ce3d0eeb7b457496dbbe623b2ff473e

Changed in glance:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.