Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[BUG] A request the HTTP Listener rejects leaves no record anywhere

Offen
  • Stimmt etwas nicht?
#480 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
backend, observability

Rechercherichtung

Start in the HTTP Listener receiver, HttpReceiver, where the existing ErrorEvent dispatch sites are, and read the Jetty hook HttpChannel.Listener.onRequestFailure that the issue identifies as the only one reporting rejected requests. Reproduce with the curl command in the issue (431 with a 9000-byte header) and check the Events tab and logs/mirth.log. Done means a rejected request produces an Events entry naming the listener, and ideally the 400 and 414 cases are covered too; conf/log4j2.properties is also involved in the logging side. The issue leaves the event design open, so confirm the approach with maintainers first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug

Describe the bug
This is the HTTP Listener source connector. When the Jetty server it runs rejects a request before the channel sees it, nothing is recorded: no message, no event, nothing in mirth.log. Same for a header that is too large (431), a URI that is too long (414) and a malformed header (400). Reproducible every time.

To Reproduce

  1. Deploy an HTTP Listener with the default Request Header Size (8192).
  2. curl -H "X-Big: $(head -c 9000 /dev/zero | tr '\0' a)" http://localhost:<port>/
  3. The client gets 431 Request Header Fields Too Large.
  4. Look at the dashboard, the Events tab and logs/mirth.log.

Expected behavior
An operator can see that the listener turned a request away, and why.

Actual behavior
Nothing anywhere. No event is written. Jetty logs a WARN, but conf/log4j2.properties sets rootLogger = ERROR with no Jetty logger, so the line is dropped.

Environment
OIE 4.6.0 (Linux tarball), OpenJDK 17.0.20.1, Jetty 9.4.57. main has the same Jetty version and the same log4j2.properties root logger.

Workaround(s)
Add to conf/log4j2.properties and restart:

logger.jettyParser.name = org.eclipse.jetty.http.HttpParser
logger.jettyParser.level = WARN

A 431 then writes WARN ... org.eclipse.jetty.http.HttpParser: Header is too large 8193>8192 to mirth.log, and a 414 writes URI is too large >8192. The line names no channel, port or client, a 400 for a malformed header still logs nothing, and there is still no event.

Additional context
Which Jetty hooks see a rejected request, checked on 9.4.57:

  • HttpChannel.Listener.onRequestFailure fires with BadMessageException: 431 (register with connector.addBean(...)). It is the only one that reports the failure.
  • ErrorHandler.handle never fires on this path.
  • RequestLog.log, onResponseBegin and onComplete fire but report status 200, so a request log would record the rejection as a success.

HttpReceiver already dispatches ErrorEvents at four sites, so an Events entry from onRequestFailure would fit. Jetty throws BadMessageException for the 400 and 414 cases too, so the same hook should cover them (not tested).

Vorherrschende Sprache
Java
Sterne
227
Forks
81
Ø Merge
2 T. 18 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus OpenIntegrationEngine/engine

Alle Issues in OpenIntegrationEngine/engine

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.