No log entries for the status code 513 response are captured in access log when exceeding request-limit filter in JBoss EAP 7.0.x

Solution Verified - Updated -

Issue

  • No log entries are captured in access log for the status code 513 response when exceeding request-limit filter in JBoss EAP 7.0.x.
  • I tested the request-limit filter with the following configuration. It works fine and the status code 513 response is returned when exceeding the limit. However, no log entries is captured for the status code 513 response in the access log:

    <subsystem xmlns="urn:jboss:domain:undertow:3.1">
        <buffer-cache name="default"></buffer>
        <server name="default-server">
            <http-listener name="default" socket-binding="http" redirect-socket="https"/>
            <host name="default-host" alias="localhost">
                ...
                <access-log pattern="%h %l %u %t "%r" %s %b "%{i,Referer}" "%{i,User-Agent}" "%{i,COOKIE}" "%{o,SET-COOKIE}" %S "%I" %T"></access>
                <filter-ref name="request-limit-filter" predicate="path-prefix('/example')"></filter>
                ...
            </host>
        </server>
        ...
        <filters>
            ...
            <request-limit name="request-limit-filter" queue-size="1" max-concurrent-requests="10"></request>
        </filters>
    </subsystem>
    

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 7.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content