-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
S3: fix Expires header behavior #12894
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
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 8m 33s ⏱️ Results for commit 979a714. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 1h 26m 1s ⏱️ Results for commit 979a714. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 4m 56s ⏱️ - 39m 23s Results for commit 979a714. ± Comparison against base commit 75858d8. This pull request removes 2670 and adds 1 tests. Note that renamed tests count towards both.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Kudos to the reporter for spotting this issue
Motivation
As reported by #12890, we had the wrong behavior with the
Expires
parameter. This was ported back from our legacy implementation, which wrong assumptions: theExpires
header is only about cache invalidation, and has nothing to do with Object Expiration, linked with lifecycle rules.This PR improves the AWS validated test, and remove the old behavior raising an Exception.
Changes
Expires
value