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

Administering Session Identifiers for Anonymous
Sessions
iTP Secure WebServer System Administrator’s Guide—522659-001
11- 3
Configuring for Anonymous Ticketing
Now the user has received one resource and makes a request for another. The web client
has retained the user’s ticket so it can be reused, as shown in Figure 11-2.
Again, the ticket is logged. Because the ticket contains a user ID that uniquely identifies
the user, the company in this example can track and analyze a user’s web activity by
generating reports based on the log file.
Refer to the iTP Secure WebServer WebReporter User’s Guide for more information
about generating reports from log files.
Two points are especially important to note in this process:
•
Tickets work with most web clients; however, the web client itself does not know
that it is sending requests that contain tickets.
•
The process is transparent to users.
Configuring for Anonymous Ticketing
This section describes how to configure the iTP Secure WebServer to support
anonymous ticketing. You can activate ticketing for specific regions of content to track
the use of some file types while ignoring others. For example, you may want to track
accesses of HTML files, but not GIF files.
To set up a content server for anonymous ticketing, configure the server with
configuration directives and Region commands in the server configuration file
(httpd.config). Some directives and commands are required and others are optional. This
section discusses the required settings. Advanced Configuration Options
on page 11-6
describes the optional settings. For more general information about the server
configuration file (httpd.config), see Appendix A, Configuration Directives.
Figure 11-2. Using a Ticket
109CDT .CDD
iTP Secure WebServer
Internet
URL Request
with ticket
Subsequent requests
are sent with the same
ticket
Requested
Resource
So the resource is
returned immediately
Web Client