Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

rgw: Ensure xmlns is consistent on S3 responses. #8526

Merged
merged 1 commit into from Apr 17, 2016
Merged

rgw: Ensure xmlns is consistent on S3 responses. #8526

merged 1 commit into from Apr 17, 2016

Commits on Apr 11, 2016

  1. rgw: Ensure xmlns is consistent on S3 responses. 

    At least one S3 client is overly strict about requiring the xmlns to be present
in server responses. Let's be strict about what we send, and continue to be lax
about what we receive.

- Put correct XMLNS in a define instead of repeating it.
- Correct XMLNS hostname: s/doc.s3.amazonaws.com/s3.amazonaws.com/
- Add XMLNS where it was missing:
-- CORSConfiguration
-- CopyObjectResult (see S3QL#190)
-- ListMultipartUploadsResult

S3QL bug ceph#190: https://bitbucket.org/nikratio/s3ql/issues/190/sq3l-should-not-rely-on-xmlns-declarations

Signed-off-by: Robin H. Johnson <robin.johnson@dreamhost.com>
    Robin H. Johnson committed Apr 11, 2016
    Configuration menu
    Copy the full SHA
    3b83001 View commit details
    Browse the repository at this point in the history