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
Not sure if this is something I can enforce on the server, or if the client needs to do this, but I noticed that for a file name like e.<random hex id>, S3 shows the file type as <random hex id>. This may be harmless, but if we can tell AWS those files are arbitrary binary data, we should.
The text was updated successfully, but these errors were encountered:
Not sure if this is something I can enforce on the server, or if the client needs to do this, but I noticed that for a file name like
e.<random hex id>
, S3 shows the file type as<random hex id>
. This may be harmless, but if we can tell AWS those files are arbitrary binary data, we should.The text was updated successfully, but these errors were encountered: