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
I noticed though that in the documentation, it says "If either of these parameters does not match the file which is uploaded in the next step, S3 will throw an error and refuse the upload."
However, the upload succeeds with a different file and even a file with a different MIME type. Also, the link can be used several times (although it expires after a given time).
Is there some configuration that needs to be done to achieve those effects or is the documentation mistaken? I couldn't find anything in the AWS documentation that suggests the signed URL is single use and that the file must match the name and type given when generating it.
The text was updated successfully, but these errors were encountered:
Thanks for this example, was just what I needed.
I noticed though that in the documentation, it says "If either of these parameters does not match the file which is uploaded in the next step, S3 will throw an error and refuse the upload."
However, the upload succeeds with a different file and even a file with a different MIME type. Also, the link can be used several times (although it expires after a given time).
Is there some configuration that needs to be done to achieve those effects or is the documentation mistaken? I couldn't find anything in the AWS documentation that suggests the signed URL is single use and that the file must match the name and type given when generating it.
The text was updated successfully, but these errors were encountered: