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-12
Ticketing Strategies
HTML and Image References
References fall into two categories: HTML and image.
HTML references include the following:
•
<a href ="xxxx">
•
<form action ="xxxx">
•
<area href="xxxx">
•
<isindex action ="xxxx">
•
<img usemaps ="xxxx">
Image references include the following:
•
<img src="xxxx">
•
<body background ="xxxx">
•
<bgsound src="xxxx">
•
<img dynsrc="xxxx">
•
<input src="xxxx">
•
<meta url="xxxx">
•
<embed src="xxxx">
•
<applet codebase ="xxxx">
•
<script src="xxxx">
For ticketing purposes, the distinction between the two types is significant because you
may want to track HTML hits but not image hits; the ticketing attributes allow you to
treat the two types of references separately.
Rewriting HTML References
By default, the server makes relative absolute HTML references when necessary.
Specifically:
•
If cookies are unavailable, or if the ForceTicketInUrl attribute has been turned on,
the server makes relative any absolute references that it can. That is, if an absolute
reference points to a file on the same server, the server converts the reference to a
relative reference. This enables the web client to attach a ticket to the URL.
•
If cookies are enabled and the web client supports them, and if the ForceTicketInUrl
attribute is off, the server does not rewrite any HTML references.
Note that the server does not modify the files stored on disk; instead, as it sends the file
to the web client, it rewrites any absolute references it finds.