S3 sometimes returns buckets from the wrong region - investigate

[Randgalt]

Ad hoc testing shows the following scenario:

• Perform s3 ls to get list of root buckets
• The buckets are not always in the requested region
• Find a bucket not in the region and try to get details: s3 ls s3://<bucket>
• S3 will return a 301 without a Location header. The only signal is the presence of the x-amz-bucket-region header that's a different region than the requested region.

Figure out the right way to handle this. Currently, it's a 500 because Jetty generates an error when the Location header is missing.