You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified all of my SDK modules are up-to-date (you can perform a bulk update with go get -u github.com/aws/aws-sdk-go-v2/...)
Related to this but appears to be enabled by default now: #1606
Describe the bug
When calling S3 GetObject and using the IfNoneMatch (for ETag caching) the SDK logs a warn message:
SDK 2025/03/02 02:10:31 WARN Response has no supported checksum. Not validating response payload.
If you remove the IfNoneMatch and the object is actually fetched, the WARN log is not printed since the checksum validation is performed properly.
Regression Issue
Select this option if this issue appears to be a regression.
Expected Behavior
The log should not be printed in cases where the object is not actually fetched.
WARN Response has no supported checksum. Not validating response payload.
Current Behavior
Prints the log when an object is not fetched due to IfNoneMatch (Not Modified). I haven't tested other ways to prevent the actual object fetch, but I suspect the same issue occurs with those.
WARN Response has no supported checksum. Not validating response payload.
adev-code
added
investigating
This issue is being investigated and/or work is in progress to resolve the issue.
needs-triage
This issue or PR still needs to be triaged.
and removed
needs-triage
This issue or PR still needs to be triaged.
investigating
This issue is being investigated and/or work is in progress to resolve the issue.
labels
Mar 3, 2025
Acknowledgements
go get -u github.com/aws/aws-sdk-go-v2/...
)Related to this but appears to be enabled by default now: #1606
Describe the bug
When calling S3 GetObject and using the IfNoneMatch (for ETag caching) the SDK logs a warn message:
If you remove the
IfNoneMatch
and the object is actually fetched, the WARN log is not printed since the checksum validation is performed properly.Regression Issue
Expected Behavior
The log should not be printed in cases where the object is not actually fetched.
Current Behavior
Prints the log when an object is not fetched due to
IfNoneMatch
(Not Modified). I haven't tested other ways to prevent the actual object fetch, but I suspect the same issue occurs with those.Reproduction Steps
Here's a simple program to demonstrate:
Possible Solution
No response
Additional Information/Context
I can work around with this, but it's annoying to have to do this:
AWS Go SDK V2 Module Versions Used
github.com/aws/aws-sdk-go-v2 v1.36.2
github.com/aws/aws-sdk-go-v2/config v1.29.7
github.com/aws/aws-sdk-go-v2/service/s3 v1.77.1
github.com/aws/smithy-go v1.22.2
Compiler and Version used
go version go1.23.6 linux/amd64
Operating System and version
AL2 5.10.234-205.895.amzn2int.x86_64
The text was updated successfully, but these errors were encountered: