Don't send ion access token to non-ion servers #7839
Merged
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.
@tfili can you review. @OmarShehata this should fix the issue you uncovered.
Some ion-hosted assets can still point to additional external servers as, part of their dataset. We were still appending the ion access_token in the Accept header to these servers, which is at best pointless but at worst would cause some CORS requests to fail because the Accept header was not allowed.