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

[gateway-s3] List Parts returns parts with ETag having doubled double quotes #4294

Closed
vadmeste opened this issue May 8, 2017 · 4 comments · Fixed by #4295
Closed

[gateway-s3] List Parts returns parts with ETag having doubled double quotes #4294

vadmeste opened this issue May 8, 2017 · 4 comments · Fixed by #4295

Comments

@vadmeste
Copy link
Member

vadmeste commented May 8, 2017

Expected Behavior

ListParts returns

...<Part><PartNumber>1</PartNumber
><LastModified>2017-05-08T18:53:09.031Z</LastModified><ETag>&#34;&#34;d9340f5267685ca716e86c33e570c12e&#34;&#34;</ETag><Size>67108864</Size></Part><Part>...

Current Behavior

ListParts returns

...<Part><PartNumber>1</PartNumber
><LastModified>2017-05-08T18:53:09.031Z</LastModified><ETag>&#34;d9340f5267685ca716e86c33e570c12e&#34;</ETag><Size>67108864</Size></Part><Part>...

Possible Solution

Steps to Reproduce (for bugs)

  1. Setup a Minio gateway instance pointing to an S3 server
  2. Setup a multipart upload and upload a part
  3. List parts

(I did this with mc after tweaking some codes to the the gateway xml response)

Context

Testing

Your Environment

All, master

@vadmeste
Copy link
Member Author

vadmeste commented May 8, 2017

Taking this.

@deekoder deekoder added this to the Release milestone May 8, 2017
@deekoder deekoder modified the milestones: GCS, Edge cache May 8, 2017
@vadmeste
Copy link
Member Author

We should add a test in mint for this case

@harshavardhana
Copy link
Member

We should add a test in mint for this case

Perhaps open a bug over at mint so that we don't forget @vadmeste

@lock
Copy link

lock bot commented May 6, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants