Request with non-unicoded HTTP headers sometimes returns 503

[Daisuke Morita]

HTTP request with non-unicoded HTTP headers (e.g., X-Account-Meta-*, X-Container-Meta-* and X-Versions-Location) fails with 503 response code. Those headers should be checked by proxy servers if they contain non-unicoded messages and return 400 Bad Request.

[Kun Huang (academicgareth)]

what's your use case making something wrong?

[Samuel Merritt (torgomatic)]

Shift-JIS, maybe?

Honestly, it doesn't really matter. A repeatable 5xx response usually indicates an unhandled exception somewhere, and those should always get fixed. A 503 probably means that the request is making it to the backend servers and those are returning 500 to the proxy, but that's speculation on my part.

I managed to reproduce this on my SAIO setup, and it looks like an unhandled UnicodeDecodeError coming out of the broker's update_metadata method, so it seems like our bogus header is making all the way to the broker before blowing up. Ugh.

[Samuel Merritt (torgomatic)]

Make sure the code you're developing on includes commit ace2aa3; this fixes a bug in object versioning with non-ASCII container names.

[OpenStack Infra (hudson-openstack)]

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

[Tianshi Li (lts9165)]

@Samuel,
Yes, i developed on the lastest master branch, and it includes your commit ace2aa3

[John Dickinson (notmyname)]

needs to be reconfirmed

[Launchpad Janitor (janitor)]

[Expired for OpenStack Object Storage (swift) because there has been no activity for 60 days.]