Configuring a Custom Undertow Filter in WildFly

Internal

• Undertow WildFly Subsystem Configuration

Example

https://github.com/NovaOrdis/playground/tree/master/wildfly/custom-undertow-filter

Overview

In order to install a custom filter in WildFly Undertow instance, you will need to wrap the filter class in a WildFly module, deploy the module and configure the Undertow subsystem to use the custom filter.

Create and Deploy a WildFly Module

In order to be made available to the Undertow subsystem, the custom filter code must be deployed as a WildFly Module. For more details on how to build and deploy a custom module, see:

Writing a Custom WildFly Module

Express the Module's Dependency on io.undertow.core

The filter code must implement so the module must have access to those classes. This is achieved by declaring the module's dependency on :

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="com.novaordis.playground.wildfly.custommodule" slot="1.0">
   ...
   <dependencies>
        <module name="io.undertow.core"/>
   </dependencies>
</module>

Configure the Undertow Subsystem

Declare the Filter in the <filters> Section

...
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
   ...
   <filters>
      ...
      <filter name="response-time" 
              class-name="com.novaordis.playground.wildfly.undertow.customfilter.ResponseTime" 
              module="com.novaordis.playground.wildfly.undertow.customfilter:1"/>
      </filters>
</subsystem>
...

Module Version

If the module has been deployed in the "main" slot, no version information is required when configuring the filter. Otherwise, the version information can be specified after the module name and the ":" separator: module="com.novaordis.playground.wildfly.undertow.customfilter:1.0".

Declare a Reference to the Filter for a Specific Host

...
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
   <server name="...">
      ...
      <host name="...">
           <location .../>
           ...
           <filter-ref name="response-time"/>
           ...
      </host>
   </server>
   ...
</subsystem>
...