fix: include additional logging in the wopicontext middleware #10101
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.
Description
Include additional logs for errors inside the wopicontext middleware.
There have been cases where the wopi server returns a 401 (unauthorized) code, which suggest a problem in the wopicontext middleware, however, there are no logs about the cause of the error, which makes it very difficult to debug.
This PR just adds new logs for error cases. There is no change in the behavior nor in the log information.
Related Issue
Related to #10053
Motivation and Context
Troubleshooting for those 401 errors should be easier.
How Has This Been Tested?
Partially tested manually by making a request to the wopi server with wrong data. Seen the "missing access token" and "failed to parse jwt token". The rest might require a more carefully crafted token, so it's more difficult to prove, but the risk is very low.
Screenshots (if appropriate):
Types of changes
Checklist: