HTTP Server Transport (com.soa.platform.jetty)

Configuration properties for the Jetty transport

Allow Cross-Context Session IDs (session.manager.factory.crossContextSessionIDs)

Allow sessions to be used in multiple contexts/applications. This applies only to web applications.

Default: true

Allow Http Only Cookies (session.manager.factory.httpOnlyCookies)

Prevents cookies from being accessed from javascript on modern Browsers. Safeguards against Cross Site scripting

Default: true

Allow Secure Cookies (session.manager.factory.secureCookies)

Encrypts cookies during when browser uses HTTPS.

Default: false

Session Idle Timeout (session.manager.factory.sessionTimeout)

The session idle timeout in seconds. This applies only to web applications.

Default: 3600

Accept Backlog (http.incoming.transport.config.acceptQueueSize)

The size of the accept socket queue. This is also known as the 'backlog'.

Default: 100

Accept Threads (http.incoming.transport.config.acceptThreads)

The number of accept threads

Default: 1

Accept Socket Timeout (http.incoming.transport.config.acceptTimeout)

The accept socket timeout in milliseconds. This is also used as the SO_TIMEOUT for incoming data sockets. Warning: setting a small value for this may result in frequent recycling of the accept socket which may cause dropped connections.

Default: 1800000

SSL Protocols (http.incoming.transport.config.enabledProtocols)

The set of SSL protocols to allow. Note that this property is only used at the time a listener is created. If a listener is already configured, changes will not take effect until the following restart.

Security protocol (http.incoming.transport.config.securityProtocol)

The default SSL protocol. With IBM stacks this should usually be set to 'SSL' or 'SSL_TLS'. Note that this property is only used at the time a listener is created. If a listener is already configured, changes will not take effect until the following restart. This may also be set for individual endpoints using the connection property 'https.security.protocol'.

Default: TLS

SSL Cipher Suites (http.incoming.transport.config.cipherSuites)

The set of SSL cipher suites allow. Note that this property is only used at the time a listener is created. If a listener is already configured, changes will not take effect until the following restart.

Non-Blocking I/O (http.incoming.transport.config.useNio)

Should blocking I/O or non-blocking I/O be used? Note that this property is only used at the time a listener is created. If a listener is already configured, changes will not take effect until the following restart.

Default: true

Enable SSL Renegotiation (http.incoming.transport.config.allowRenegotiate)

Enable/disable all client SSL renegotiations. Note that this property is only used at the time a listener is created. If a listener is already configured, changes will not take effect until the following restart.

Default: true

Incoming Request Buffer Size (http.incoming.transport.config.requestBufferSize)

Set the size of the incoming request buffer in bytes. A value of 0 will use the Jetty internal default of 16K.

Default: 0

Incoming Header Buffer Size (http.incoming.transport.config.requestHeaderSize)

Set the size of the incoming header buffer in bytes. A value of 0 will use the Jetty internal default of 6K. This buffer is used to hold the request line and headers.

Default: 32768

Response Buffer Size (http.incoming.transport.config.responseBufferSize)

Set the size of the response buffer in bytes. A value of 0 will use the Jetty internal default of 16K.

Default: 0

Response Header Buffer Size (http.incoming.transport.config.responseHeaderSize)

Set the size of the response header buffer in bytes. A value of 0 will use the Jetty internal default of 6K.

Default: 32768

Use X-Forward headers (http.incoming.transport.config.forwarded)

Uses X-Forward headers to calculate HttpServletRequest attributes. Useful if container is accessed using a reverse proxy.

Default: false

Incoming Request Queue Size (http.incoming.transport.config.requestQueueSize)

Set the size of the incoming request queue for listeners. A change to this value requires a restart.

Default: 16

Max Connections Per Client (http.incoming.transport.config.maxConnectionsPerClient)

Set the maxmimum number of concurrent connections from a single client. A value of 0 indicates no limit. Note that if running behind a layer 7 load balancer, this constraint will restrict the number of connections from the load balancer, not the originating client, and therefore should not be used under those circumstances. If this limit is exceeded, the incoming connection is simply closed.

Default: 0

Max Requests Per Client (http.incoming.transport.config.maxRequestsPerClient)

Set the maxmimum number of concurrent requests from a single client. A value of 0 indicates no limit. If running behind a layer 7 load balancer, the http.incoming.transport.config.forwarded property must be set in order to properly interpret the X-Forwarded- headers. If this limit is exceeded, the client will receive a 503 (Service Unavailable) response.

Default: 0

Enable NCSA Access Log (ncsa.access.log.enable)

Enable/disable the NCSA access log.

Default: false

Enable Extended Log Format (ncsa.access.log.extended)

Enable/disable the extended log format.

Default: false

NCSA Access Log Filename (ncsa.access.log.filename)

The filename to use for the NCSA access log. The filename should include the string 'yyyy_mm_dd', which is replaced with the actual date when creating and rolling over the file.

Default: ${product.home.dir}/instances/${container.name}/log/access_yyyy_mm_dd.log

NCSA Access Log Retention (ncsa.access.log.retainDays)

The number of days to retain log files for the NCSA access log.

Default: 30

NCSA Access Log Append (ncsa.access.log.append)

Control whether to append or overwrite log files for the NCSA access log.

Default: true

NCSA Access Log Latency (ncsa.access.log.logLatency)

Show the request processing time in the NCSA access log.

Default: true

Enable Status Servlet (jetty.information.servlet.enable)

Enable the Jetty status servlet. Default path to status page is /admin/com.soa.transport.jetty/information

Default: false

Max Form Keys (context.manager.maxFormKeys)

Set the max number of keys allowed in a form. If not specified or 0, the default of 1000 is used.

Default: 0

Max Form Size (context.manager.maxFormSize)

Set the max size in bytes allowed in a form. If not specified or 0, the default of 200K is used.

Default: 0

Enable Sessions (context.manager.enableSessions)

Enable/disable session support globally.

Default: true

Strict Context Matching (context.manager.strict)

Enable or disable strict context matching. If set to true, only the first context selected by Jetty will be used. If the request is not satisfied by that context, then no others will be tried.

Default: false

Enable Statistics Gathering (connector.manager.stats)

Enable or disable statistics gathering for connectors

Default: true

Send Date Header (jetty.server.sendDateHeader)

Force Jetty to send a Date header in responses. The default is false internally but the spec requires servers to send a Date if possible. See http://jira.codehaus.org/browse/JETTY-1137

Default: true

Send Server Header (jetty.server.sendServerVersion)

Force Jetty to send a Server header in responses.

Default: false

Response Header Templates (response.header.generator.templates)

Response headers that will be generated based on the value of a template. Valid template property names are: incoming.scheme, incoming.hostname, incoming.port, incoming.path, incoming.uri, now (the current time as a long value), or the name of any available request header (case-insensitive). Template properties are enclosed in braces, e.g. {now}. If a variable cannot be found then the template variable will appear as the header value. If allowSystemProperties is set to true, any system properties may also be included. Note that blocked header rules in the transport do not impact these headers. The value is a comma-separated list,

Default: Strict-Transport-Security:max-age=31536000includeSubDomains

Response Header Generation Contexts (response.header.generator.contexts)

Specify the list of contexts for which generation of response headers will be performed. This is a comma-separated list of context paths that will have header generation applied.

Enable Response Header Generation (response.header.generator.enable)

Enable/disable generation of response headers.

Default: false

Enable Response Header System Properties (response.header.generator.allowSystemProperties)

Allow system properties in generation of response headers.

Default: false