Skip to content

Clarify what makes URL browser incompatible #3019

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
Feb 9, 2022

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Feb 9, 2022

Motivation and Context

Clarify somewhat confusing behavior.

Modifications

Javadoc update to clarify that checksum validation makes URL browser incompatible.

Testing

N/A javadoc update.

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

@dagnir dagnir requested a review from a team as a code owner February 9, 2022 01:47
* S3Presigner presigner = S3Presigner.builder()
* .serviceConfiguration(S3Configuration.builder()
* .checksumValidationEnabled(false)
* .accelerateModeEnabled(true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we remove accelerateModeEnabled? It seems we are suggesting it needs to be enabled to be browser compatible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to show a "real world" use case when a customer might want to specify a custom S3Configuration in the first place, but that's a good point. I removed it and clarified the S3Configuration use case in the docs.

@dagnir dagnir force-pushed the s3-presigner-url-checksum-browser branch from be57c10 to 1b4d1c6 Compare February 9, 2022 18:23
@dagnir dagnir force-pushed the s3-presigner-url-checksum-browser branch from 1b4d1c6 to 4d2a9c2 Compare February 9, 2022 18:26
@dagnir dagnir enabled auto-merge (squash) February 9, 2022 18:32
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 9, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@dagnir dagnir merged commit 01d3a11 into aws:master Feb 9, 2022
@dagnir dagnir deleted the s3-presigner-url-checksum-browser branch February 9, 2022 19:17
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.

2 participants