10.02.2013 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MIME<br />

types<br />

and<br />

header<br />

filtering<br />

v<br />

[filter-content-types]<br />

v<br />

[filter-request-headers]<br />

[filter-content-types]<br />

stanza<br />

type<br />

=<br />

type_name<br />

List<br />

of<br />

entries<br />

that<br />

specify<br />

MIME<br />

types<br />

to<br />

be<br />

filtered<br />

by<br />

<strong>WebSEAL</strong><br />

when<br />

received<br />

from<br />

junctioned<br />

servers.<br />

Administrators<br />

can<br />

add<br />

additional<br />

MIME<br />

types<br />

that<br />

refer<br />

to<br />

a<br />

document<br />

that<br />

contains<br />

HTML<br />

or<br />

HTML-like<br />

content.<br />

This<br />

list<br />

of<br />

stanza<br />

entries<br />

is<br />

required.<br />

Do<br />

not<br />

remove<br />

the<br />

default<br />

entries.<br />

Default<br />

list<br />

entries:<br />

type<br />

=<br />

text/html<br />

type<br />

=<br />

text/vnd.wap.wml<br />

See<br />

“Standard<br />

URL<br />

filtering<br />

rules<br />

<strong>for</strong><br />

<strong>WebSEAL</strong>”<br />

on<br />

page<br />

288<br />

[filter-request-headers]<br />

stanza<br />

header<br />

=<br />

header_name<br />

List<br />

of<br />

HTTP<br />

headers<br />

that<br />

<strong>WebSEAL</strong><br />

filters<br />

be<strong>for</strong>e<br />

sending<br />

the<br />

request<br />

to<br />

a<br />

junctioned<br />

server.<br />

A<br />

default<br />

list<br />

is<br />

built-in<br />

to<br />

<strong>WebSEAL</strong>.<br />

The<br />

default<br />

entries<br />

are<br />

not<br />

included<br />

in<br />

the<br />

configuration<br />

file.<br />

Default<br />

list:<br />

host<br />

connection<br />

proxy-connection<br />

expect<br />

te<br />

iv-ssl-jct<br />

iv-user<br />

iv_user<br />

iv-groups<br />

iv_groups<br />

iv-creds<br />

iv_creds<br />

iv_remote_address<br />

iv-remote-address<br />

The<br />

addition<br />

of<br />

new<br />

entries<br />

in<br />

this<br />

stanza<br />

is<br />

optional.<br />

For<br />

example,<br />

an<br />

administrator<br />

could<br />

add<br />

the<br />

header<br />

accept-encoding.<br />

This<br />

would<br />

instruct<br />

<strong>WebSEAL</strong><br />

to<br />

remove<br />

any<br />

accept-encoding<br />

headers<br />

from<br />

requests<br />

be<strong>for</strong>e<br />

<strong>for</strong>warding<br />

the<br />

request<br />

to<br />

the<br />

junction.<br />

The<br />

removal<br />

of<br />

the<br />

accept-encoding<br />

header<br />

would<br />

cause<br />

the<br />

junction<br />

server<br />

to<br />

return<br />

the<br />

document<br />

in<br />

an<br />

unencoded<br />

<strong>for</strong>m,<br />

allowing<br />

<strong>WebSEAL</strong><br />

to<br />

filter<br />

the<br />

document<br />

if<br />

necessary.<br />

New<br />

entries<br />

must<br />

consist<br />

of<br />

valid<br />

HTTP<br />

headers.<br />

Appendix<br />

A.<br />

<strong>WebSEAL</strong><br />

configuration<br />

file<br />

reference<br />

463

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!