Manual Part 2

Wireless Array
Configuring the Wireless Array 197
Proxy forwarding on the Array is designed for proxy servers such as Blue Coat
and Netbox Blue whose purpose is restricting Internet access to sites, applications
and content, and the monitoring and reporting of this activity. It is not used for
enhanced performance utilizing content caching.
Proxy forwarding on the Array is configured as described in “Procedure for
Configuring Proxy Forwarding on the Array” on page 203. This proxies all HTTP
traffic to the specified server. If you wish to proxy HTTPS traffic as well, you must
take the additional steps described below.
Proxy Forwarding for HTTPS
There are two usage scenarios for proxy forwarding:
 Use proxy forwarding for HTTP traffic only: set up the Array per
“Procedure for Configuring Proxy Forwarding on the Array” on
page 203. HTTPS traffic is unaffected and proceeds in the usual way.
 Use proxy forwarding for both HTTP and HTTPS traffic: set up the Array
per “Procedure for Configuring Proxy Forwarding on the Array” on

SSID and client User Name restrictions permit the following characters. 
— Blue Coat permits only alphanumerics and + and /. 
— Netbox Blue permits only alphanumerics and dot, hyphen, underscore,
and space characters.

Blue Coat policy configuration: 
The AuthConnector utility is not used with the Xirrus implementation.
Traffic must first be passed through the portal to dynamically add the User
to Blue Coat’s list of recognized Users, based on the User header inserted in
the packets. When configuring Blue Coat Content Filtering policy, you may
select “Users from Reporting”. Only the User value can be used in this
manner. The Group header value is not dynamically added to Blue Coat’s
Group list, and it can't be added manually.
Netbox Blue policy configuration:

Users and Groups are manually configured on the server. Users are
manually assigned to Groups, and policy is applied on a per-Group basis.