Jetty 12 ComplianceViolation.Listener not notified for URI, Cookie, and Multipart violations. #11253
Assignees
Labels
Milestone
Comments
joakime
added
Bug
|
Note: HTTP/1 violations are properly notified. |
joakime
added a commit
that referenced
this issue
Jan 8, 2024
… URI / MultiPart compliance to also receive listener events.
joakime
added a commit
that referenced
this issue
Jan 16, 2024
joakime
added a commit
that referenced
this issue
Jan 24, 2024
… URI / MultiPart compliance to also receive listener events. (#11254) + Introduce new events on `ComplianceViolation.Listener` + Introduce new `ComplianceViolation.Listener.initialize()` to allow for a new Listener at the appropriate time (to support per-request listeners) + Introduce new `ComplianceViolation.CapturingListener` + Introduce new `HttpConfiguration.(add/remove/get)ComplianceViolationListener()` methods. + Deprecate/Remove handling of `recordComplianceViolations` in `HttpConnection` and `HttpConnectionFactory` classes. + Produce warnings if use of `ComplianceViolation.Listener` as beans is still present. + Add `ComplianceViolation.Listener` support to `UriCompliance` locations. + Add `ComplianceViolation.Listener` support to `MultiPartCompliance` locations. + Add `ComplianceViolation.Listener` support to `CookieCompliance` locations. + Add `ComplianceViolation.Listener` support to `HttpCompliance` locations in HTTP/2 and HTTP/3 --------- Co-authored-by: gregw <[email protected]>
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Jetty 12.0.6 FROZEN
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
12.0.5
Jetty Environment
core / ee10 / ee9 / ee89
Java version/vendor
(use: java -version)Any
OS type/version
Any
Description
The
ComplianceViolation.Listeneris not called for Cookie, URI, and Muiltipart violations.The text was updated successfully, but these errors were encountered: