yahoo-eng-team team mailing list archive

[Erno Kuvaja <jokke@xxxxxx>]

"""
These headers:
x-image-meta-container_format: bare
x-image-meta-disk_format: qcow2
x-image-meta-is_public: True

are not valid HTTP headers - these should not contain underscores.
"""

This is not accurate statement. 
RFC 822:
3.1.2.  STRUCTURE OF HEADER FIELDS
"""
The  field-name must be composed of printable ASCII characters (i.e., characters that  have  values  between  33.  and  126., decimal, except colon).
"""
and rfc 2616 sec 4.2 refers the format to rfc 822.

So it's nginx breaking the protocol by stripping those, not us by using
them and as that 'underscores_in_headers on|off' has been on nginx at
least from 2011 already I don't see reason why this should be bug in
glance.

** Changed in: glance
       Status: Confirmed => Invalid

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

Title:
  Glance uses INVALID HTTP header names - with underscore in their name

Status in OpenStack Image Registry and Delivery Service (Glance):
  Invalid

Bug description:
  These headers:
  x-image-meta-container_format: bare
  x-image-meta-disk_format: qcow2
  x-image-meta-is_public: True

  are not valid HTTP headers - these should not contain underscores.

  HTTP proxies such as nginx (which are used e.g. for SSL termination)
  strip these headers by default.

  I believe it is a bug since Glance should be HTTP-compliant.

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