fix: Use force-cache
when fetching debug IDs
#78456
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When fetching JavaScript source files to get their debug IDs, we leave the cache setting as default which means:
default
— The browser looks for a matching request in its HTTP cache.In the case of fetching debug IDs, we are not bothered about the cache match being fresh or stale. Regardless of the staleness, the source file in the cache is much more likely to be the code that is currently executing.
force-cache
— The browser looks for a matching request in its HTTP cache.Using
force-cache
can result in less conditional requests checking if the source has changed.Of course, Sentrys JavaScript assets might be so heavily cached that this makes little to no difference!