> This fix relaxes the constraints on user set authentication headers. > Currently, any user set authentication headers are filtered out, if the > HttpClient has an Authenticator set. The reason being that the authenticator > is expected to manage authentication. With this fix, it will be possible to > use pre-emptive authentication through user set headers, even if an > authenticator is set. The expected use case is where the authenticator would > manage either proxy or server authentication and the user set headers would > manage server authentication if the authenticator is managing proxy (or vice > versa). > If the pre-emptive authentication fails, then this behavior is disabled on > further retries and it would be up to the authenticator to provide the right > credentials then. > > Thanks, > Michael
Michael McMahon has updated the pull request incrementally with one additional commit since the last revision: Update src/java.net.http/share/classes/java/net/http/HttpClient.java Co-authored-by: Daniel Fuchs <67001856+df...@users.noreply.github.com> ------------- Changes: - all: https://git.openjdk.org/jdk/pull/21249/files - new: https://git.openjdk.org/jdk/pull/21249/files/1e8b42b6..68dde1ee Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=21249&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=21249&range=01-02 Stats: 3 lines in 1 file changed: 1 ins; 0 del; 2 mod Patch: https://git.openjdk.org/jdk/pull/21249.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/21249/head:pull/21249 PR: https://git.openjdk.org/jdk/pull/21249
