IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

v
“Processing
URLs
in
requests”
on
page
292
v
“Handling
cookies
from
servers
across
multiple
-j
junctions”
on
page
295
Understanding
path
types
used
in
URLs
Any
HTML
page
is
likely
to
contain
URLs
(links)
to
other
resources
on
that
back-end
server
or
elsewhere.
URL
expressions
can
appear
in
the
following
formats:
v
relative
v
server-relative
v
absolute
Links
containing
URLs
expressed
in
relative
format
never
require
any
manipulation
by
WebSEAL.
By
default,
the
browser
handles
relative
URLs
in
links
by
prepending
the
correct
scheme,
server,
and
directory
information
(including
the
junction)
to
the
relative
URL.
The
prepended
information
is
derived
from
the
request
URL
for
the
page
on
which
the
link
is
located.
Example
relative
URL
expressions:
abc.html
../abc.html
./abc.html
sales/abc.html
However,
difficulties
arise
with
server-relative
and
absolute
path
formats.
Links
to
back-end
resources
expressed
in
absolute
or
server-relative
formats
succeed
only
if
WebSEAL
was
able
to
modify
the
URL
path
expression
and
include
junction
information.
Example
server-relative
URL
expressions:
/abc.html
/accounts/abc.html
Example
absolute
URL
expression:
http://www.tivoli.com/abc.html
Note:
All
programmers
of
Web
scripts
are
encouraged
to
use
relative
links
(not
absolute
or
server-relative)
for
dynamically
generated
URLs.
Filtering
URLs
in
responses
This
section
describes
how
WebSEAL
filters
URLs
in
responses
from
junctioned
back-end
application
servers.
v
“Standard
URL
filtering
rules
for
WebSEAL”
on
page
288
v
“Modifying
absolute
URLs
with
script
filtering”
on
page
290
v
“Filtering
changes
the
Content-Length
header”
on
page
290
v
“Limitation
with
unfiltered
server-relative
links”
on
page
291
Standard
URL
filtering
rules
for
WebSEAL
WebSEAL
uses
a
set
of
standard
rules
to
filter
URLs
contained
in
pages
that
are
responses
to
client
requests.
To
apply
standard
URL
filtering,
WebSEAL
must
be
able
to
″see″
the
URLs
on
a
page
sent
from
the
back-end
server.
WebSEAL
cannot
use
standard
filtering
rules
for
URLs
embedded
in
scripts.
By
default,
WebSEAL
filters
only
documents
of
MIME
type
″text/html″
and
″text/vnd.wap.wml″
that
are
received
from
junctioned
servers.
Additional
MIME
types
can
be
configured
using
the
[filter-content-types]
stanza
of
the
WebSEAL
configuration
file.
288
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide