24e2847af2
Today we do not preserve response headers if they are present on a transport protocol response. While preserving these headers is not always desired, in the most cases we should pass on these headers to have consistent results for depreciation headers etc. yet, this hasn't been much of a problem since most of the deprecations are detected early ie. on the coordinating node such that this bug wasn't uncovered until #22647 This commit allow to optionally preserve headers when a context is restored and also streamlines the context restore since it leaked frequently into the callers thread context when the callers context wasn't restored again. |
||
|---|---|---|
| .. | ||
| fixtures | ||
| framework | ||
| logger-usage | ||
| build.gradle | ||