Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-11829

(7.1.0) AjpRequestParser does not output any log message when exceeding max-parameters/max-headers

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.1.0.ER2
    • None
    • Undertow
    • None

    Description

      http listener output the following DEBUG log message when exceeding max-parameters/max-headers. However, ajp listener does not output any log mssage. ajp listener should output DEBUG log like http listener.

      DEBUG [io.undertow.request.io] (default I/O-31) UT005014: Failed to parse HTTP request: io.undertow.server.protocol.http.HttpRequestParser$BadRequestException: UT000039: To many query parameters, cannot have more than 5 query parameters
	at io.undertow.server.protocol.http.HttpRequestParser.handleQueryParameters(HttpRequestParser.java:523)
	at io.undertow.server.protocol.http.HttpRequestParser.beginQueryParameters(HttpRequestParser.java:450)
	at io.undertow.server.protocol.http.HttpRequestParser.handlePath(HttpRequestParser.java:374)
	at io.undertow.server.protocol.http.HttpRequestParser.handle(HttpRequestParser.java:215)
	at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:185)
	at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:134)
	at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:148)
	at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:92)
	at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:51)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
	at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:130)
	at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:588)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:468)

      DEBUG [io.undertow.request.io] (default I/O-41) UT005014: Failed to parse HTTP request: io.undertow.server.protocol.http.HttpRequestParser$BadRequestException: UT000040: To many headers, cannot have more than 5 header
	at io.undertow.server.protocol.http.HttpRequestParser.handleHeaderValueCacheMiss(HttpRequestParser.java:720)
	at io.undertow.server.protocol.http.HttpRequestParser.handleHeaderValue(HttpRequestParser.java:657)
	at io.undertow.server.protocol.http.HttpRequestParser.handle(HttpRequestParser.java:256)
	at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:185)
	at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:134)
	at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:148)
	at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:92)
	at io.undertow.server.protocol.http.HttpOpenListener.handleEvent(HttpOpenListener.java:51)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:291)
	at org.xnio.ChannelListeners$10.handleEvent(ChannelListeners.java:286)
	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
	at org.xnio.nio.QueuedNioTcpServer$1.run(QueuedNioTcpServer.java:130)
	at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:588)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:468)

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-1020 AjpRequestParser does not output any log message when exceeding max-parameters/max-headers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11830 (7.0.z) UNDERTOW-1020 AjpRequestParser does not output any log message when exceeding max-parameters/max-headers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              thofman Tomas Hofman
              Jan Stourac Jan Stourac
              Jan Stourac Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: