Technical data

Setting Up WebLogic Server for HTTP Tunneling
Configuring and Managing WebLogic Server 7-23
MaxPostSize
Limits the number of bytes of data received in a POST from a single request. If
this limit is triggered, a
MaxPostSizeExceeded exception is thrown and the
following message is sent to the server log:
POST size exceeded the parameter MaxPostSize.
An HTTP error code 413 (Request Entity Too Large) is sent back to the client.
If the client is in listening mode, it gets these messages. If the client is not in
listening mode, the connection is broken.
Setting Up WebLogic Server for HTTP
Tunneling
HTTP tunneling provides a way to simulate a stateful socket connection between
WebLogic Server and a Java client when your only option is to use the HTTP protocol.
It is generally used to tunnel through an HTTP port in a security firewall. HTTP is a
stateless protocol, but WebLogic Server provides tunneling functionality to make the
connection appear to be a regular T3Connection. However, you can expect some
performance loss in comparison to a normal socket connection.
Configuring the HTTP Tunneling Connection
Under the HTTP protocol, a client may only make a request, and then accept a reply
from a server. The server may not voluntarily communicate with the client, and the
protocol is stateless, meaning that a continuous two-way connection is not possible.
WebLogic HTTP tunneling simulates a T3Connection via the HTTP protocol,
overcoming these limitations. There are two attributes that you can configure in the
Administration Console to tune a tunneled connection for performance. You access
these attributes in the Servers section, under the Connections and Protocols tabs. It is
advised that you leave them at their default settings unless you experience connection
problems. These properties are used by the server to determine whether the client
connection is still valid, or whether the client is still alive.