OpenSearch/client
Tim Vernum 8a89306aaf
Preserve REST client auth despite 401 response (#30558)
The default behaviour for Apache HTTP client is to mimic the standard
browser behaviour of clearing the authentication cache (for a given
host) if that host responds with 401.
This behaviour is appropriate in a interactive browser environment
where the user is given the opportunity to provide alternative
credentials, but it is not the preferred behaviour for the ES REST
client.

X-Pack may respond with a 401 status if a request is made before the
node/cluster has recovered sufficient state to know how to handle the
provided authentication credentials - for example the security index
need to be recovered before we can authenticate native users.
In these cases the correct behaviour is to retry with the same
credentials (rather than discarding those credentials).
2018-05-17 18:27:18 +10:00
..
benchmark Clients: Switch to new performRequest (#30543) 2018-05-14 10:37:53 -04:00
client-benchmark-noop-api-plugin Build: Mostly silence warning about html4 javadoc (#30220) 2018-04-28 09:50:54 -04:00
rest Preserve REST client auth despite 401 response (#30558) 2018-05-17 18:27:18 +10:00
rest-high-level Rest High Level client: Add List Tasks (#29546) 2018-05-16 13:31:37 +02:00
sniffer Remove animal sniffer from REST client sniffer (#30260) 2018-05-01 09:33:17 +02:00
test Introduce elasticsearch-core jar (#28191) 2018-01-15 09:59:01 -07:00
transport Add rank-eval module to transport client and HL client dependencies 2017-12-13 18:05:43 +01:00