Transport HTTP Documentation

Overview

The transport HTTP bundle provides both an HTTP channel for other bundles to use and also an inbound HTTP dispatcher for various application containers to use.

Using the dispatcher

The HTTP dispatcher encapsulates configuration and handling of inbound HTTP chains listening for traffic. Once a request arrives, it will fire an event that any available HTTP containers can check against their applications and either claim or ignore. It provides request/response handling in the com.ibm.websphere.http package, which is similar but simpler than a servlet spec of the HTTP traffic.


Steps to use:

Using the channel

Other bundles can use the HTTP inbound or outbound channels in their own chains, simply by including the channel type of "HTTPInboundChannel" or "HTTPOutboundChannel" in their channel/chain configurations. They would then program against the HTTP channel and GenericBNF public APIs (com.ibm.wsspi.http.channel and com.ibm.wsspi.genericbnf).

Using the EncodingUtils

The EncodingUtils DS component provides string locale and converter methods. It has locale mappings that used to ship in WAS property files. It also has internal pooling of locale and supported encodings for faster use.

Using the HttpDateFormat

The HTTP date format service provides apis for creating and formatting, or parsing, various HTTP date formats. This contains all the necessary logic for handling the multiple possible HTTP date formats, from plain ASCII to various RFC definitions. It internally uses threadlocal SimpleDateFormat objects to reduce the overhead as much as possible for users of the service.

RequestContext queries

HTTP dispatcher provides various HTTP information through the request context. Using the GlobalContext service, the /request/http queries are routed to the HTTP dispatcher's current request on that Event thread. Valid queries include:

Bundle configuration