Undertow WildFly Subsystem Configuration
Jump to navigation
Jump to search
External
- EAP 7.0 Beta Configuration Guide https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/7.0.beta/configuration-guide/chapter-9-configuring-the-web-server-undertow
Internal
Overview
...
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
<buffer-cache name="default"/>
<server name="default-server">
<http-listener name="default" redirect-socket="https" socket-binding="http"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<filter-ref name="server-header"/>
<filter-ref name="x-powered-by-header"/>
</host>
</server>
<servlet-container name="default">
<jsp-config/>
<websockets/>
</servlet-container>
<handlers>
<file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>
</handlers>
<filters>
<response-header name="server-header" header-value="JBoss-EAP/7" header-name="Server"/>
<response-header name="x-powered-by-header" header-value="Undertow/1" header-name="X-Powered-By"/>
</filters>
</subsystem>
...
Schema
Configuration Elements
buffer-cache
server
http-listener
The HTTP listener uses the XNIO Worker declared and configured by the io subsystem. The XNIO worker's configuration is described here worker.
Note that the this http listener is also used by JBoss Remoting HTTP connector, so if the name of the listener changes, the http-connector's connector-ref should be changed accordingly.