Bump org.apache.httpcomponents.core5:httpcore5 from 5.2.1 to 5.2.4

[dependabot]

Bumps org.apache.httpcomponents.core5:httpcore5 from 5.2.1 to 5.2.4.

Changelog

Sourced from org.apache.httpcomponents.core5:httpcore5's changelog.

Release 5.2.4

This is a maintenance release that corrects a major defect discovered since release 5.2.3 that can lead to an H2 connection failing at runtime with the message "Frame size exceeds maximum" when executing requests with an enclosed message body and the remote endpoint having negotiated a maximum frame size larger than the protocol default (16KB).

Change Log

• HTTPCORE-762: H2 protocol handler incorrectly determines the maximum frame size for outgoing frames in case the remote endpoint negotiated a max frame size larger than the protocol default. Contributed by Oleg Kalnichevski

Release 5.2.3

This is a maintenance release that corrects several defects discovered since release 5.2.2 including a major defect that can cause non-blocking character-based consumers to enter an invalid state and stop processing incoming data.

Change Log

• HTTPCORE-757: AbstractCharDataConsumer fails to correctly handle incomplete UTF8 encoded data split across multiple data packets. Contributed by Oleg Kalnichevski

• Support SOCKS5 with username/password authentication Contributed by yndu13

• Non-blocking protocol handler to filter out non-printable ASCII and non-ASCII characters from HTTP headers by default. This makes the behavior of the non-blocking transport consistent with that of the blocking one (#416). Contributed by vismayku

• HTTPCORE-754: StrictConnPool fails to correctly handle infinite request timeout. Contributed by Oleg Kalnichevski

• HTTPCORE-753: Fixed race condition in the IOSession#close method. Contributed by Oleg Kalnichevski

Release 5.2.2

... (truncated)

Commits

• 8fd744d HttpCore 5.2.4 release
• c5a5301 Updated release notes for HttpCore 5.2.4 release
• faaa82f HTTPCORE-762: H2 protocol handler incorrectly determines the maximum frame si...
• 0d4aeb5 Add security warning to TrustStrategy documentation (#438)
• 371347a HTTPCLIENT-2298: Strict connection pool to filter out expired and completed r...
• e3c770b Upgraded HttpCore version to 5.2.4-SNAPSHOT
• 5425ae1 Updated release notes for HttpCore 5.2.3 release
• 6f8f579 HTTPCORE-757: AbstractCharDataConsumer fails to correctly handle incomplete U...
• bfba5f9 Deprecated misplaced method that introduced a dependency between the protocol...
• f44526e Support SOCKS5 proxy with username/password authentication
• 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)