Metadata keys are not case sensitive

I would take it one step further and say it should be "case persistent" or something.

For me, what I see is that only the first letter is caps. X-Object-Meta-CookieSD becomes X-Object-Meta-Cookiesd

HTTP spec already indicates header names are case insensitive. I can't imagine a use case where case should matter and that use case be a correct one. :)

gholt: HTTP is just one possible interface, and its limitations shouldn't define the contract of the OpenStack storage system. The HTTP spec doesn't prevent us from doing the right thing, so we should.

HTTP is the only interface right now, and probably the only one planned. That said, if you'd like to submit a patch for this, have at it. You'll have to patch the container server's db layer and webob at a minimum. And, even so, whoever consumes the HTTP interface should *not* assume any particular case.

Based on the discussion, marking as invalid in swift and converting to a docbug

Fix proposed to branch: master
Review: https://review.openstack.org/13065

https://review.openstack.org/#/c/13065/

Reviewed: https://review.openstack.org/13065
Committed: http://github.com/openstack/openstack-manuals/commit/0983861fd4728f2fde8bf475860b04efa005a116
Submitter: Jenkins
Branch: master

commit 0983861fd4728f2fde8bf475860b04efa005a116
Author: Tom Fifield <email address hidden>
Date: Sun Sep 16 18:07:55 2012 +1000

    Add a note about metadata case senstivity in swift

    fixes bug 939982

    As in the bug report, the Swift interface uses HTTP which has no
    case sensitivity. This patch adds a note to remind users not to
    expect it.

    Change-Id: I6b1bcae84bea40d17b062f1d98bb465766c5c3b9