Comment 2 for bug 1244613

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.