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

Administering Session Identifiers for Anonymous
Sessions
iTP Secure WebServer System Administrator’s Guide—523346-002
11- 3
Ticketing and Tracking Example
.
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:
Figure 11-1. Requesting a Ticket
Figure 11-2. Using a Ticket
107CDT .CDD
Web Client
iTP Secure WebServer
Internet
URL Request
Redirect to
URL with ticket
No ticket, so...
This time, there is a
ticket, so...
URL Request,
with ticket
Requested
resource
iTP Secure WebServer
generates ticket
and sends a redirect to
the web client.
the resource
is returned.
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