WildFly 8.0 Model Reference

  1. WildFly 8.0
  2. subsystem=undertow
  3. server
  4. ajp-listener

http listener

Attributes (18)

  • allow-encoded-slash If a request comes in with encoded / characters (i.e. %2F), will these be decoded.
    • Attribute Value
    Default Value false
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • always-set-keep-alive If this is true then a Connection: keep-alive header will be added to responses, even when it is not strictly required by the specification.
    • Attribute Value
    Default Value true
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • buffer-pipelined-data If we should buffer pipelined requests.
    • Attribute Value
    Default Value true
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • buffer-pool The AJP listeners buffer pool
    • Attribute Value
    Default Value default
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-write
    Restart Required all-services
  • decode-url If this is true then the parser will decode the URL and query parameters using the selected character encoding (UTF-8 by default). If this is false they will not be decoded. This will allow a later handler to decode them into whatever charset is desired.
    • Attribute Value
    Default Value true
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • enabled If the listener is enabled
    • Attribute Value
    Default Value true
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required all-services
  • max-buffered-request-size Maximum size of a buffered request, in bytesRequests are not usually buffered, the most common case is when performing SSL renegotiation for a POST request, and the post data must be fullybuffered in order to perform the renegotiation.
    • Attribute Value
    Default Value 16384
    Type INT
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • max-cookies The maximum number of cookies that will be parsed. This is used to protect against hash vulnerabilities.
    • Attribute Value
    Default Value 200
    Type INT
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • max-header-size The maximum size in bytes of a http request header.
    • Attribute Value
    Default Value 51200
    Type INT
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • max-headers The maximum number of headers that will be parsed. This is used to protect against hash vulnerabilities.
    • Attribute Value
    Default Value 200
    Type INT
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • max-parameters The maximum number of parameters that will be parsed. This is used to protect against hash vulnerabilities.This applies to both query parameters, and to POST data, but is not cumulative (i.e. you can potentially have max parameters * 2 total parameters).
    • Attribute Value
    Default Value 1000
    Type INT
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • max-post-size The maximum size of a post that will be accepted
    • Attribute Value
    Default Value 10485760
    Type LONG
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • record-request-start-time If this is true then Undertow will record the request start time, to allow for request time to be logged. This has a small but measurable performance impact
    • Attribute Value
    Default Value false
    Type BOOLEAN
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • redirect-socket If this listener is supporting non-SSL requests, and a request is received for which a matching requires SSL transport, undertow will automatically redirect the request to the socket binding port specified here.
    • Attribute Value
    Default Value https
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-write
    Restart Required resource-services
  • scheme The listener scheme, can be HTTP or HTTPS. By default the scheme will be taken from the incoming AJP request.
    • Attribute Value
    Type STRING
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required all-services
  • socket-binding The AJP listener socket binder
    • Attribute Value
    Type STRING
    Nillable false
    Expressions Allowed false
    Storage configuration
    Access Type read-write
    Restart Required all-services
  • url-charset URL charset
    • Attribute Value
    Default Value UTF-8
    Type STRING
    Nillable true
    Expressions Allowed true
    Storage configuration
    Access Type read-write
    Restart Required no-services
  • worker The AJP listeners XNIO worker
    • Attribute Value
    Default Value default
    Type STRING
    Nillable true
    Expressions Allowed false
    Storage configuration
    Access Type read-write
    Restart Required all-services

Operations (2)

  • add Add listener
    Request Parameter Type Required Expressions Allowed Default value Description
    enabled BOOLEAN false true true If the listener is enabled
    always-set-keep-alive BOOLEAN false true true If this is true then a Connection: keep-alive header will be added to responses, even when it is not strictly required by the specification.
    buffer-pipelined-data BOOLEAN false true true If we should buffer pipelined requests.
    redirect-socket STRING false false https If this listener is supporting non-SSL requests, and a request is received for which a matching requires SSL transport, undertow will automatically redirect the request to the socket binding port specified here.
    record-request-start-time BOOLEAN false true false If this is true then Undertow will record the request start time, to allow for request time to be logged. This has a small but measurable performance impact
    allow-encoded-slash BOOLEAN false true false If a request comes in with encoded / characters (i.e. %2F), will these be decoded.
    decode-url BOOLEAN false true true If this is true then the parser will decode the URL and query parameters using the selected character encoding (UTF-8 by default). If this is false they will not be decoded. This will allow a later handler to decode them into whatever charset is desired.
    url-charset STRING false true UTF-8 URL charset
    socket-binding STRING true false The AJP listener socket binder
    buffer-pool STRING false false default The AJP listeners buffer pool
    max-header-size INT false true 51200 The maximum size in bytes of a http request header.
    max-headers INT false true 200 The maximum number of headers that will be parsed. This is used to protect against hash vulnerabilities.
    max-cookies INT false true 200 The maximum number of cookies that will be parsed. This is used to protect against hash vulnerabilities.
    scheme STRING false true The listener scheme, can be HTTP or HTTPS. By default the scheme will be taken from the incoming AJP request.
    max-post-size LONG false true 10485760 The maximum size of a post that will be accepted
    max-parameters INT false true 1000 The maximum number of parameters that will be parsed. This is used to protect against hash vulnerabilities.This applies to both query parameters, and to POST data, but is not cumulative (i.e. you can potentially have max parameters * 2 total parameters).
    worker STRING false false default The AJP listeners XNIO worker
    max-buffered-request-size INT false true 16384 Maximum size of a buffered request, in bytesRequests are not usually buffered, the most common case is when performing SSL renegotiation for a POST request, and the post data must be fullybuffered in order to perform the renegotiation.
  • remove Listener name