Issue #5170 - fix upgrade bug in HttpReceiverOverHTTP #5266
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.
Fixes a bug introduced when fixing issue #5170.
The
HttpExchange
could be null when the response completes inHttpReceiverOverHTTP
, in this case we end incorrectly continue reading and parsing in theHttpReceiverOverHttp
, and this can result inReadPendingException
and other issues including losing the websocket data.I have also cleaned up the debug logging in websocket to prevent the same stacktrace being logged at every level. They should only be logged in
processConnectionError()
andprocessHandlerError()
.