Execution order of defined filters in undertow is inconsistent

Solution In Progress - Updated -

Issue

  • Undertow filter execution order ignored
  • We have defined three different filters in the undertow subsystem (see full undertow subsystem config below):
<filter-ref name="custom-proxy-filter"/> - custom Handler class to accept only requests from defined DNs
<filter-ref name="eap-ssl-headers"/>  - EAP's standard ssl-headers handler
<filter-ref name="gzipfilter"/>        - EAP's standard gzip filter
  • It seems that the eap-ssl-headers is executed as first when the first request hitting undertow contains the ssl_client_cert header.
    • If the first request does not contain the ssl_client_cert header, the custom-proxy-filter is executed as first.
      This differs from the behaviour in EAP 7.0.8 and EAP 6.4.x where the filters were executed in the configuration order

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 7.1.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.