chore(deps): Bump jetty from 12.1.10 to 12.1.11

[dependabot]

Bumps jetty from 12.1.10 to 12.1.11.
Updates org.eclipse.jetty:jetty-bom from 12.1.10 to 12.1.11

Release notes

Sourced from org.eclipse.jetty:jetty-bom's releases.

12.1.11

Changelog

• #15345 - Move RateControl to jetty-io
• #15308 - CachingWebAppClassLoader is not registering as parallel capable
• #15267 - Introduce module for MinimumDataRateHandler
• #15234 - Review error response codes from EagerContentHandler
• #15232 - Jetty 12.1.x EE11 doesn't handle Session attributes properly
• #15228 - Fix increased in memory usage between 12.1.8 and 12.1.10 caused by ZipFileSystems
• #15226 - Server becomes inaccessible with thousands of qtp threads blocked in HttpChannelState.onIdleTimeout ReentrantLock
• #15217 - jetty-quic-quiche-foreign fails on Windows due to eager resolution of Unix-only quiche_conn_set_keylog_fd
• #15156 - Injecting authentication headers using request filters

Commits

• 6c1ced3 Updating to version 12.1.11
• 852c52d Cleanup javadoc for recently deprecated Context newResource methods. (#15354)
• ce0c7f5 Issue #15234 - Review error response codes from EagerContentHandler and FormF...
• 994f8b1 Updates to #15224 - Retain explicit HTTP version in redirects.
• fae1edd [httpclient] forward httpversion for http:// uri on request.copy to avoid to ...
• 7192101 Fixes #15345 - Move RateControl to jetty-io.
• 65c44e0 #15333 upgrade quiche to version 0.29.2
• 0f096b5 Bump actions/stale from 10.2.0 to 10.3.0 (#15166)
• 1defd98 [12.1.x EE8] Bump the spec-deps group across 1 directory with 2 updates (#15102)
• 6315bce Merge pull request #15287 from jetty/fix/jetty-12.1.x/15156-InjectingAuthHead...
• Additional commits viewable in compare view

Updates org.eclipse.jetty:jetty-http from 12.1.10 to 12.1.11

Updates org.eclipse.jetty:jetty-server from 12.1.10 to 12.1.11

Updates org.eclipse.jetty.http2:jetty-http2-common from 12.1.10 to 12.1.11

Updates org.eclipse.jetty.http2:jetty-http2-hpack from 12.1.10 to 12.1.11

Updates org.eclipse.jetty.http2:jetty-http2-server from 12.1.10 to 12.1.11

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 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)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	org.eclipse.jetty/​jetty-http@​12.1.10 ⏵ 12.1.11
	org.eclipse.jetty/​jetty-server@​12.1.10 ⏵ 12.1.11	-44		+9		-30

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: maven org.eclipse.jetty:jetty-server is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: gradle/libs.versions.toml → maven/org.eclipse.jetty/jetty-server@12.1.11 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/org.eclipse.jetty/jetty-server@12.1.11. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report