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: handle unrecognized values for Expires in responses #2653

Merged
merged 2 commits into from
May 23, 2024
Merged

Conversation

lucix-aws
Copy link
Contributor

Fixes #2652, see that issue for context.

DO NOT MERGE without merging aws/smithy-go#512.

@lucix-aws lucix-aws requested a review from a team as a code owner May 22, 2024 20:50
@lucix-aws lucix-aws merged commit c6c1626 into main May 23, 2024
12 of 13 checks passed
@lucix-aws lucix-aws deleted the fix-s3expires branch May 23, 2024 15:51
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.

Customize S3's "Expires" field to handle invalid timestamps
2 participants