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.

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

S3 put bucket should not require content-length - Veritas #2816

Closed
tamireran opened this issue Mar 24, 2017 · 4 comments
Closed

S3 put bucket should not require content-length - Veritas #2816

tamireran opened this issue Mar 24, 2017 · 4 comments
Labels
S3-Compatibility S3 Compatibility and Namespace over AWS Severity 1 Unable to use product / product is unable to operate / product caused other critical sw to fail

Comments

@tamireran
Copy link
Contributor

Environment info

  • Version: 1.2.0-b2d8e03
  • Deployment: AZURE
  • Customer: Veritas

Actual behavior

1.Veritas test script tries to create a new bucket without content-length
According to AWS documents, it's not mandatory (see the last example)

http://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUT.html

Expected behavior

  1. Validate content length only if exists for PUT requests (create bucket only)

Steps to reproduce

  1. I'm using veritas script, you can use whatever

Screenshots or Logs or other output that would be helpful

(If large, please upload as attachment)

@tamireran tamireran added S3-Compatibility S3 Compatibility and Namespace over AWS Priority 1 Critical Severity 1 Unable to use product / product is unable to operate / product caused other critical sw to fail labels Mar 24, 2017
@tamireran
Copy link
Contributor Author

@nimrod-becker I currently commented it in the test environment, but I will need it in an official version.

The problem is in s3_rest.js, check_headers. We need to differentiate between put object and put bucket.

@guymguym
Copy link
Member

Duplicate of #2586.
I have a fix not yet merged to master.

@tamireran
Copy link
Contributor Author

tamireran commented Mar 24, 2017

+1

ETA?

@nimrod-becker
Copy link
Contributor

Dup, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S3-Compatibility S3 Compatibility and Namespace over AWS Severity 1 Unable to use product / product is unable to operate / product caused other critical sw to fail
Projects
None yet
Development

No branches or pull requests

3 participants