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
{{ message }}
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
buckets and objects are the primary resources, and objects are stored in buckets. Amazon S3 has a flat structure instead of a hierarchy like you would see in a file system. However, for the sake of organizational simplicity, the Amazon S3 console supports the folder concept as a means of grouping objects. Amazon S3 does this by using a shared name prefix for objects
A "folder" is nothing but a convention for objects with a trailing / in their name in the S3 console or web UI.
It's fine if fake-s3 stores objects in the file system hierarchy as an implementation detail, but this should not leak into the observable behavior. One problem that this creates is #151, another is that path normalisation means when I PUTa/b/c.x into my bucket, I can not only access (GET) it by a/b/c.x but also a/b/../b/c.x. These should be separate objects though.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
According to https://docs.aws.amazon.com/AmazonS3/latest/user-guide/using-folders.html
A "folder" is nothing but a convention for objects with a trailing
/
in their name in the S3 console or web UI.It's fine if fake-s3 stores objects in the file system hierarchy as an implementation detail, but this should not leak into the observable behavior. One problem that this creates is #151, another is that path normalisation means when I
PUT
a/b/c.x
into my bucket, I can not only access (GET
) it bya/b/c.x
but alsoa/b/../b/c.x
. These should be separate objects though.The text was updated successfully, but these errors were encountered: