OpenSearch/client/rest
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
..
licenses Update REST client deps license and notice files (#25573) 2017-07-06 16:52:17 +02:00
src Preserve REST client auth despite 401 response (#30558) 2018-05-17 18:27:18 +10:00
build.gradle Remove animal sniffer from low-level REST client (#29646) 2018-04-25 22:41:30 -04:00