fix: 404 not found when intercepting the ingestion key calls #5490
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
[Issue]: the baseURL for
gatewayAPIwas missing the trailing/due to which when the interception happens due to token expiry the new URL formed has a missing/. It doesn't cause any issue in the normal flow but only in interception because we do a substring(1) from the URL to remove the leading/. Now since both the slashes are missing we form a bad URL and hence we get 404 not found error.Related Issues / PR's
fixes #5468
Screenshots
NA
Affected Areas and Manually Tested Areas