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
Upgrading from moto 3.1.11, we found the following issue: Our prefixes foo%2Fbar now get interpreted as foo/bar, but only in prefixes (be it in plain list_objects_v2 or with Delimiter='/' directory listing). Here's a quick repro that works on 3.1.11 and breaks on 3.1.12 (same with all the other repros here):
I tried the same thing (manually, no repro here) with AWS S3 and found the behaviour to match 3.1.11.
One last repro: here's where it gets confusing - Delimiter='/'-style listing looks like it's listing a nested directory, but that goes against the principle of that functionality:
Upgrading from moto 3.1.11, we found the following issue: Our prefixes
foo%2Fbar
now get interpreted asfoo/bar
, but only in prefixes (be it in plainlist_objects_v2
or withDelimiter='/'
directory listing). Here's a quick repro that works on 3.1.11 and breaks on 3.1.12 (same with all the other repros here):The Prefix no longer matches the Key, here's my output:
Here's a different repro with a directory listing.
I tried the same thing (manually, no repro here) with AWS S3 and found the behaviour to match 3.1.11.
One last repro: here's where it gets confusing -
Delimiter='/'
-style listing looks like it's listing a nested directory, but that goes against the principle of that functionality:Which yields
Looking at the commits between 3.1.11 and 3.1.12, it would seem like this was the offending pull request - #5181 - but I haven't bisected this.
Let me know if you want more repros or details.
Thanks!
The text was updated successfully, but these errors were encountered: