Manual Part 2

Wireless Array
198 Configuring the Wireless Array
page 203. Then you must set up browsers on client stations (laptops,
smart phones, tablets, ...) to proxy both HTTP and HTTPS traffic to the
Array. Each client must also download and install the SSL certificate from
the Blue Coat or Netbox Blue proxy server. Follow the procedure below to
perform these steps on each client. Note that when a proxy is set up and
used for HTTPS, HTTP traffic will also use the proxy server, so configure
both as instructed in “Configuring Proxy Forwarding on Clients for
HTTPS” on page 199.
Summary of Proxy Forwarding Behavior on the Array
If proxy forwarding is not enabled in the Array and the client browser is not
configured to use a proxy:
HTTP traffic (port 80) and HTTPS traffic (port 443) pass transparently
through the Array in the usual way.
If proxy forwarding is enabled for Blue Coat or Netbox Blue and the client
browser is not configured to use a proxy (i.e., you do not wish to proxy secure
traffic):
The browser still uses HTTP (port 80) and this traffic is captured and
proxied by the Array.
The browser still uses HTTPS (port 443) and this traffic is passed
transparently through the Array.
If proxy forwarding is not working correctly, HTTP traffic (port 80) is
blocked.
If proxy forwarding is enabled for Blue Coat or Netbox Blue and the client
browser is configured to use a proxy:
The browser is configured to proxy HTTPS to www.xirrus.com port 4388.
The browser automatically proxies HTTP traffic to the same port that is
used for HTTPS traffic—port 4388.
All HTTP/HTTPS traffic is captured by the Array and proxied to Blue
Coat or Netbox Blue per your settings.
If Array proxy forwarding is not working correctly (for example, if the
configuration is incorrect), all HTTP/HTTPS/4388 traffic is blocked.