Bump org.apache.httpcomponents.client5:httpclient5 from 5.4.1 to 5.4.2 in /java-client

[dependabot]

Bumps org.apache.httpcomponents.client5:httpclient5 from 5.4.1 to 5.4.2.

Changelog

Sourced from org.apache.httpcomponents.client5:httpclient5's changelog.

Release 5.4.2

This is a maintenance release that upgrades HttpCore to version 5.3.3 and fixes several regressions reported since the last release. One of the regressions could cause connection leaks and eventual connection pool exhaustion in case of proxy authentication failure when establishing a tunnel via the proxy.

Change Log

• Upgraded HttpCore to version 5.3.3 Contributed by Oleg Kalnichevski

• Improved internal state representation of the internal async execution runtime in order to prevent potential race conditions. Contributed by Oleg Kalnichevski

• HTTPCLIENT-2357, regression: Classic HttpClient fails to release connection in case of a proxy authentication failure. Contributed by Oleg Kalnichevski

• HTTPCLIENT-2355, regression: Reset protocol version in the execution context on a 200 response to CONNECT request. Contributed by Oleg Kalnichevski

• HTTPCLIENT-2354: ResponseCachingPolicy to allow caching of responses with "must-revalidate" in shared caches with Authorization headers. The change aligns with RFC 9111 Section 5.2.2.2 (#609). Contributed by Arturo Bernal

• Do not add Upgrade header if Connection header already present (the caller manually manages connection state). Contributed by Oleg Kalnichevski

• Avoid logging HTTP message version where it can be a hint, not an actual protocol version Contributed by Oleg Kalnichevski

• IDN encode hostnames with Unicode characters prior to DNS resolution (#608). Contributed by Arturo Bernal

• HTTPCLIENT-2353: Fixed rejection of certificates with IDN encoded identities. (#607) Contributed by Arturo Bernal

Commits

• 34f1b02 HttpClient 5.4.2 release
• 2145d2c Updated release notes for HttpClient 5.4.2 release
• 7e48abb Upgraded HttpCore to version 5.3.3
• 1119d49 Disabled a test case that fails intermittently with GitHub Actions, pending r...
• 9433bca Improved internal state representation of the internal async execution runtim...
• 7f56b8e HTTPCLIENT-2357, regression: Classic HttpClient fails to release connect in c...
• 8958b36 HTTPCLIENT-2355, regression: Reset protocol version in the execution context ...
• f7f8069 Upgraded HttpCore to version 5.3.2
• d048550 Fix HTTPCLIENT-2354 by updating ResponseCachingPolicy to allow caching of res...
• 5ab09ea Do not add Upgrade header if Connection header already present (the calle...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/opensearch-java/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/opensearch-java/backport-2.x
# Create a new branch
git switch --create backport/backport-1401-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b6a9d9374335231c233d6c01b1ac81f59f29ee60
# Push it to GitHub
git push --set-upstream origin backport/backport-1401-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/opensearch-java/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-1401-to-2.x.