fix: Console error on some cross-origin requests without NR CAT header #1407
+4
−5
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.
XHR headers will be checked for the deprecated New Relic CAT header before calling
getResponseHeader
, which throws a console error if it does not exist for cross-origin requests.Overview
getResponseHeader
behavior when dealing with a nonexistent header:Access-Control-Expose-Headers
… which is the case for all response from the test-server.Related Issue(s)
https://new-relic.atlassian.net/browse/NR-371864
Testing
Non-error (cannot be tracked via JSErrors feat) + difficult to test for.