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 Apr 6, 2022. It is now read-only.
Our current implementation for an upload profile picture feature works perfectly under our HTTP staging deployment. However, on production (with same keys just for testing) using HTTPS, the upload fails with 403 no matter what and gives the following error:
I've tried modifying the S3 policy, CORS configuration with no luck. Also, the same keys and configuration are working for plain HTTP access. It is the only (relevant) difference at this point and can't seem to find any clue! Any help will be greatly appreciated.
Thanks in advance!
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.
Hi!
Our current implementation for an upload profile picture feature works perfectly under our HTTP staging deployment. However, on production (with same keys just for testing) using HTTPS, the upload fails with 403 no matter what and gives the following error:
My bucket policy (
production-url.com
is production andbeta.production-url.com
is staging):And the CORS configuration:
I've tried modifying the S3 policy, CORS configuration with no luck. Also, the same keys and configuration are working for plain HTTP access. It is the only (relevant) difference at this point and can't seem to find any clue! Any help will be greatly appreciated.
Thanks in advance!
The text was updated successfully, but these errors were encountered: