We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The docs say that headObject should return a NoSuchKeyException when not found.
It does not throw NSKE. Instead, it throws an ordinary:
S3Exception null (Service: S3Client; Status Code: 404; Request ID: null) software.amazon.awssdk.core.http.pipeline.stages.HandleResponseStage.handleErrorRes\ ponse (HandleResponseStage.java:114)
#147 appeared to fix this for getObject, but headObject still busted (there's even a test for it in that changeset.)
HEAD a non existent key with the S3Client
JDK 10 + AWS SDK v2 preview 10
The text was updated successfully, but these errors were encountered:
I will add, I really don't care for throwing exceptions in such a common case. HEAD will either return stat meta or not.
Sorry, something went wrong.
Also see #297
This has been fixed as part of #830 and will be included in the next release.
Merge pull request #544 from aws/staging/ca1f986f-55eb-49fb-8bf5-40af…
20f2920
…c7d8e32d Pull request: release <- staging/ca1f986f-55eb-49fb-8bf5-40afc7d8e32d
No branches or pull requests
Expected Behavior
The docs say that headObject should return a NoSuchKeyException when not found.
Current Behavior
It does not throw NSKE. Instead, it throws an ordinary:
#147 appeared to fix this for getObject, but headObject still busted (there's even a test for it in that changeset.)
Steps to Reproduce (for bugs)
HEAD a non existent key with the S3Client
Your Environment
JDK 10 + AWS SDK v2 preview 10
The text was updated successfully, but these errors were encountered: