Deploying the Webcache in Your Network 33
Deploying the
Webcache in Your
Network
You must determine how you are going to deploy the Webcache in your
network. The Webcache can be deployed in two ways:
■ Proxy Cache mode — The Webcache is connected to a Layer 2 switch
in your LAN. You must configure the Web browser on each client
machine in your network to direct its Web requests to the Webcache.
■ Transparent Cache mode — The Webcache is connected to a Layer 4
redirection device — a switch, router or firewall in your LAN which is
capable of Redirection. No configuration of the Web browser on each
client machine is needed because the Layer 4 device automatically
redirects Web requests to the Webcache.
CAUTION: 3Com recommends that you deploy your Webcache on the
LAN side of a firewall, or on the SuperStack 3 Firewall's DMZ port as
described in “Deploying the SuperStack 3 Firewall as a Proxy Forwarder”
on page 35.
The term “Web requests” refers to three types of network traffic; HTTP,
HTTPS (SSL encrypted) and HTTP-FTP. The Webcache can accept all of
these traffic types. In Proxy Cache mode, you should configure the Web
browser on each client machine to use the Webcache as the server for
each of these protocols.
HTTPS (SSL encrypted) traffic is only passed through by the Webcache; it
is not decoded or cached.
Proxy Cache
Figure 9 Proxy Cache Deployment
Server
Server
Client Machine
Client Machine
Client Machine
WANLAN
WANGateway
W
h
S
u
p
e
r
S
t
a
c
k
3
®
3
C
1
6
1
1
6
We
b
c
a
c
h
e
3
0
0
0
P
ow
e
r/Se
lf
tes
t
A
c
tiv
ity
C
ac
he
S
to
rag
e
S
tatus
gree
n
=
o
k
yellow
=
fa
ile
d
gre
en
=
1
0
0
M
bp
s
ye
llo
w
=
1
0
M
b
ps
L
in
k
Sta
tus
3
1
2
C
a
c
h
e
S
to
ra
g
e
S
ta
tu
s
3
2
L
in
k
S
ta
tu
s
A
c
tiv
ity
L
A
N
L
A
N
L
A
N
WA
N
