Remove header set for uninitialized response. #4963
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.
One of our groups was seeing the following stack track
In the stack trace, t_state.hdr_info.client_response is not yet initialized, so eventually things crash because of null heaps. Looking through the response logic, I think it is sufficient the just set t_state.client_info.keep_alive. The build_response logic will look at that flag and set the connection header appropriately. We have been running with that patch internally and it seems to have fixed the issue.