iTP Secure WebServer System Administrator's Guide (iTPWebSvr 5.1+)

Introduction to the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—522659-001
1-4
Features and Standards Supported by iTP Secure
WebServer
•
Session tracking and authentication
The iTP Secure WebServer includes built-in support for ticketing, a technique for
user-session tracking. The iTP Secure WebServer issues anonymous tickets.
You can use the iTP WebReporter log-analysis tool to generate reports detailing
user-access patterns.
•
Virtual hosts
The iTP Secure WebServer supports multiple domains within a single instance of
the iTP Secure WebServer, including the ability to return customized content based
on the destination domain name. Several configuration directives and configuration
directives options (for example, Region).are provided to support this capability (for
example, Accept).
•
Built-in clickable images
You can create image maps for clickable images, enabling users to easily navigate to
other pages.
•
National Center for Supercomputing Applications (NCSA) format in image maps
The iTP Secure WebServer supports NCSA-formatted image-map files in addition to
the CERN format. The iTP Secure WebServer also provides support for the point
directive in NCSA-formatted image maps.
•
Byte-range protocol
The iTP Secure WebServer supports the proposed Byte Range Retrieval Extension
to HTTP. This means, for example, that the iTP Secure WebServer can send Adobe
Portable Document Format (PDF) documents one page at a time, rather than an
entire document at once, to users of the Adobe Acrobat Reader version 3.0 or later.
This method permits high-quality PDF documents to be displayed like HTML
documents.
•
Content encoding (compression) types
This feature allows the iTP Secure WebServer to return the proper encoding type for
compressed files.
•
Administration server
The iTP Secure WebServer Administration Server provides a web-browser interface
for defining the iTP Secure WebServer configuration, starting and stopping the iTP
Secure WebServer, and monitoring noteworthy events such as errors.
•
PUT, OPTIONS, and TRACE request methods
A browser or web client (using HTTP/1.1) uses the PUT request method to replace
or create the content at a specified location. The iTP Secure WebServer accepts PUT
requests and lets you specify a script to perform validation before permitting an
update.