This documentation is for WSO2 Carbon 4.2.0. View documentation for the latest release.
Page Comparison - HTTP Servlet Transport (v.7 vs v.8) - Carbon 4.2.0 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

HTTP servlet transport should be configured in the $PRODUCT_HOMEthe <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file. The transport class that should be specified in the catalina-server.xml file is as follows: 

Code Block
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"/>

Parameter Name

Description

Possible Values

Default Value

port

The port over which this transport receiver listens for
incoming messages.

A positive integer less than 65535

9763 for HTTP Connector

9443 for HTTPS Connector

redirectPortIf this Connector is supporting non-SSL requests, and a request is received for which a matching <security-constraint> requires SSL transport, Catalina will automatically redirect the request to the port number specified here.A positive integer less than 655359443
bindOnInitControls when the socket used by the connector is bound. By default it is bound when the connector is initiated and unbound when the connector is destroyed. If set to false, the socket will be bound when the connector is started and unbound when it is stopped. false

proxyPort

When used, this transport listener will accept messages arriving through a HTTP proxy server which listens on the specified proxy port. Apache mod_proxy should be enabled on the proxy server. All the WSDLs generated will contain the proxy port value as the listener port.

A positive integer less than 65535

 

maxHttpHeaderSize

The maximum size of the HTTP request and response header
in bytes.

A positive integer

4096

acceptorThreadCountThe number of threads to be used to accept connections. Increase this value on a multi CPU machine, although you would never really need more than 2. Also, with a lot of non keep alive connections, you might want to increase this value as well.  2

maxThreads

The maximum number of worker threads created by the receiver to handle incoming requests. This parameter largely determines the number of concurrent connections that can be handled by the transport.

A positive integer

40

minSpareThreadsThe minimum number of threads always kept running. If not specified, the default will be used. 50

enableLookups

Use this parameter to enable DNS lookups in order to return the actual host name of the remote client. Disabling DNS lookups at transport level generally improves performance. By default, DNS lookups are disabled.

true, false

false

disableUploadTimeout

This flag allows the servlet container to use a different, longer connection timeout while a servlet is being executed, which in the end allows either the servlet a longer amount of time to complete its execution, or a longer timeout during data upload.

true, false

true

connectionUploadTimeoutSpecifies the timeout, in milliseconds, to use while a data upload is in progress. This only takes effect if disableUploadTimeout is set to false.  

clientAuth

Set to true if you want the SSL stack to require a valid certificate chain from the client before accepting a connection. Set to want if you want the SSL stack to request a client Certificate, but not fail if one is not present. A false value (which is the default) will not require a certificate chain unless the client requests a resource protected by a security constraint that uses CLIENT-CERT authentication.

true, false, want

false

maxKeepAliveRequests

The maximum number of HTTP requests which can be pipelined until the connection is closed by the server. Setting this attribute to 1 will disable HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining. Setting this to -1 will allow an unlimited amount of pipelined or keep-alive HTTP requests.

-1 or any positive integer

100

acceptCount

The maximum queue length for incoming connection requests when all possible request processing threads are in use. Any requests received when the queue is full will be refused.

A positive integer

10

serverOverrides the Server header for the http response. If set, the value for this attribute overrides the Tomcat default and any Server header set by a web application. If not set, any value specified by the application is used. Any stringWSO2 Carbon Server

compression

The Connector may use HTTP/1.1 GZIP compression in an attempt to save server bandwidth.

The acceptable values for the parameter is "off" (disable compression), "on" (allow compression, which causes text data to be compressed), "force" (forces compression in all cases), or a numerical integer value (which is equivalent to "on", but specifies the minimum amount of data before the output is compressed). If the content-length is not known and compression is set to "on" or more aggressive, the output will also be compressed. If not specified, this attribute is set to "off".

on, off, force

off

compressionMinSize

If compression is set to "on" then this attribute may be used to specify the minimum amount of data before the output is compressed.

A positive integer2048

noCompressionUserAgents

Indicate a list of regular expressions matching user-agents of HTTP clients for which compression should not be used, because these clients, although they do advertise support for the feature, have a broken implementation.

A comma separated list of
regular expressions

empty string

compressableMimeType

Use this parameter to indicate a list of MIME types for which HTTP compression may be used.

A comma separated list of
valid mime types

text/html, text/xml, text/plain

URIEncodingThis specifies the character encoding used to decode the URI bytes, after %xx decoding the URL.URI encoding Character set nameISO-8859-1

...