-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
mock_s3 fails to check for syntatically valid but invalid keys #3884
Comments
Raised a PR for this #3886 😄 |
@bblommers |
Just a heads up before someone closes |
@amarjandu
I agree with this comment by @bblommers. I checked the document and there is no update for version formatting of s3 object. How about adding a comment about this incompleteness to the code? |
From a comment I made in one of the earlier threads, this is how S3 behaves in regards to error messages:
If I remember correctly, the
Moto should behave the same way IMO, so we differentiate in which error we show, depending on whether the VersionID exists anywhere. Once that is implemented, I think we can close this. |
mock_s3 fails to check if a VersionID specified is syntactically correct yet invalid key.
In the two requests below:
invalid
is used, this throws a InvalidVersionID as expected.AWS behavior:
Expected: A random UUID4 string passed in as a VersionID should throw a NoSuchVersion exception as seen above.
Replication of bug on moto https://gist.github.com/amarjandu/334ffd668dd849991ba9949a32dcc3b8
Related to #2710
The text was updated successfully, but these errors were encountered: