Simon Willnauer 24e2847af2 Streamline foreign stored context restore and allow to perserve response headers (#22677) ... 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.		2017-01-18 16:17:54 +01:00
..
fixtures	in the plugin: guard against HADOOP_HOME in environment on any platform.	2015-12-21 02:21:53 -05:00
framework	Streamline foreign stored context restore and allow to perserve response headers (#22677)	2017-01-18 16:17:54 +01:00
logger-usage	Fix logger usage checker for Log4j 2	2016-09-21 14:44:14 +02:00
build.gradle	Add authentication to reindex-from-remote	2016-07-27 14:17:41 -04:00