yahoo-eng-team team mailing list archive

[Abhishek Kekane <1108979@xxxxxxxxxxxxxxxxxx>]

Glance does not support V1 and its has been removed since Ussuri.

** Changed in: glance
       Status: Triaged => Won't Fix

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

Title:
  v1 headers are not decoded

Status in Glance:
  Won't Fix

Bug description:
  In the v1.1 API, metadata headers are assumed to be ASCII-only (which
  is the case in python-glanceclient currently - see bug 1108969).
  However, in theory they could be encoded in a number of ways. If bug
  1008969 is to be fixed, glance needs to support decoding the headers
  using the MIME header encoding rules from RFC 2047
  (http://www.ietf.org/rfc/rfc2047.txt ).

  For reference the format of the header field contents is defined in
  section 4.2 of RFC 2616:

         field-content  = <the OCTETs making up the field-value
                          and consisting of either *TEXT or combinations
                          of token, separators, and quoted-string>

  http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2

  ...which must be further interpreted using section 2.2:

    The TEXT rule is only used for descriptive field contents and values
    that are not intended to be interpreted by the message parser. Words
    of *TEXT MAY contain characters from character sets other than
    ISO-8859-1 only when encoded according to the rules of RFC 2047.

         TEXT           = <any OCTET except CTLs,
                          but including LWS>

  http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html#sec2.2

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