iTP Secure WebServer System Administrator's Guide (Version 7.0)

Introduction to the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-012
1-6
iTP Secure WebServer Architecture
establishment of a persistent connection for a set of related requests; you can set a
timeout or specify the maximum number of requests per connection.
•
Chunked-transfer encoding
When a browser or Web client cannot anticipate the length of a request, it can
transmit the data in chunks to the iTP Secure WebServer. The iTP Secure
WebServer reassembles the request and processes it.
The iTP Secure WebServer supports chunked-transfer encoding.
•
Content negotiation
When a page is available in multiple representations (for example, if the text is
available in multiple languages, or a file is available in different character sets or
compression formats), the iTP Secure WebServer can select among those
representations on the basis of information transmitted with each request or
specified in the iTP Secure WebServer configuration.
iTP Secure WebServer Architecture
Figure 1-1 on page 1-7 shows the architecture for a conventional TCP/IP environment.
Descriptions of the major components follow. For information about other products, you
can use in the iTP Secure WebServer environment, see iTP Secure WebServer
Encryption on page 1-11.
If you use the new TCP/IPv6 or the Parallel Library TCP/IP product, the architectural
environment changes slightly. Running with the Auto-Accept feature, an iTP Secure
WebServer no longer needs the Distributor component. The httpd servers will assume
the listening in addition to the distributing functions of the Distributor. The Distributor
server class will be completely removed from the PATHWAY environment. All the
necessary process hops will be removed, resulting in a far superior performance.”