fix: solve client api request that can't handle 302 redirects #4352
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.
What type of PR is this?
/kind bug
What this PR does / why we need it
Whenever the token is about to expire, a new token will be obtained through refresh_token, and then a 302 redirect will occur. However, the client cannot handle the redirect normally, which will cause some errors on the page.
Therefore, we should adjust the logic here and use the new token to continue subsequent request processing so that the client can obtain the correct API request result.
Some error page rendering phenomena:
home page
pod detail page
Which issue(s) this PR fixes
Links #
Special notes for reviewers
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc