.Bucket creations in a secondary zone no longer fail Previously, when a secondary zone forwards a `create_bucket` request with a location constraint, the bucket sets the `content_length` to a non-zero value. However, the `content_length` is not parsed on the primary zone when forwarded from the secondary zone. As a result, when running a `create_bucket` operation and the `content_length` is `0` with an existing payload hash, the bucket fails to replicate. With this fix a request body is included when the `create_bucket` operation is forwarded to the primary zone and the bucket is created as expected.