I’m attempting to activate Sentry on a site built with React. Without Sentry, I’m able to access files from an AWS S3 bucket without any issues, but once I activate Sentry I’m hit with CORS errors. Looking at the request headers, the only differences I see are the absence of the Pragma and Cache-Control parameters with Sentry. In the examples below the origin is different as Sentry is currently running on a staging server and not on the live site, but I have activated it on the live site with the same results as well.
Is there a workaround for this?
Without Sentry
GET /events/merged-events-paet.json HTTP/1.1
Host: aws-fetch.s3.amazonaws.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Origin: https://afsp.org
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
With Sentry
GET /events/merged-events-paet.json undefined
Host: aws-fetch.s3.amazonaws.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
sentry-trace: 4420a5e14e7446c588b1e456f23b95bd-a81bacb5bb968f8e-1
Origin: https://staging--reverent-payne-b0d24a.netlify.app
Connection: keep-alive