Skip to content

Check the x-amz-content-range header for GetObject responses when the Content-Range header is not returned by the service. #1861

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

Merged
merged 1 commit into from
May 26, 2020

Conversation

millems
Copy link
Contributor

@millems millems commented May 26, 2020

We're still investigating this issue (S3 behaving inconsistently) internally, but this issue has lingered for long enough. No reason for people to suffer while we try to sort out the laundry.

Fixes #1209.

@millems millems merged commit f11ba79 into master May 26, 2020
@millems millems deleted the millem/fix-1209 branch May 26, 2020 21:57
@sonarqubecloud
Copy link

SonarCloud Quality Gate failed.

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

77.8% 77.8% Coverage
0.0% 0.0% Duplication

warning The version of Java (1.8.0_252) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11.
Read more here

aws-sdk-java-automation pushed a commit that referenced this pull request Dec 2, 2021
Revert "[JUnit 5] Migrate tests which can be easily converted (#2878)…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

S3's GetObjectResponse.contentRange() returns null with range request
2 participants