fetching a presigned S3 link works perfectly in development but throws a CORs error when deployed to
Unanswered
Spectacled bear posted this in #help-forum
Spectacled bearOP
My buckets are currently configured to be wide open (in development still), and everything works well in development. For some reason the production branch on Vercel is having CORs issues.
What could cause this in deployments but not in development? the URL thats used for the request is the pre-signed one, so I know Im not entering the wrong URL or endpoint.
What could cause this in deployments but not in development? the URL thats used for the request is the pre-signed one, so I know Im not entering the wrong URL or endpoint.