Repository navigation
Been receiving 404s for loader bundle #10331
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
Loader bundle fetching most recent
Framework Version
No response
Link to Sentry event
No response
SDK Setup
No response
Steps to Reproduce
It works most of the time, but on several occasions I've received 404s when getting the loader bundle for the past couple of days. You may need to clear your cdn cache?
https://js.sentry-cdn.com/10cf54c34fb7408b8d125f8f2995368d.min.js
Expected Result
Not to get 404s
Actual Result
Sometimes get 404s with the body /* not found */
Activity
AbhiPrasad commentedon Jan 24, 2024
Hey @erikt9 thanks for writing in!
So looking at our internal stats we do have a rise in 404s in our loader endpoint. (This is powered by our new metrics product). Sentry link to those who have access.
Let me follow up with our internal teams to see what is going on.
AbhiPrasad commentedon Jan 24, 2024
Internal slack thread: https://sentry.slack.com/archives/C039ZGT5K/p1706135970060269
AbhiPrasad commentedon Jan 24, 2024
Apologies for the trouble - we created an incident to track the issue and we'll respond as soon as we figure out what is going on!
erikt9 commentedon Jan 24, 2024
For whatever it's worth, when hitting the loader script in Postman, I can fix the 404 if I pass
Cache-Control: no-cachein the request headers. So it seems like the cdn is caching the 404 and returning that as the result, but asking it to not use its cached value with theCache-Controlheader works.lforst commentedon Jan 25, 2024
This incident should be resolved. Please let us know you have any more issues!