Management and Configuration Guide Supplement 4.4.0.50

HTTP Proxy Configuration per Access Policy

■ Configure the Access Points to function as RADIUS clients within the

802.1X/WPA Authentication service.

See “Configuring the 802.1X/WPA Authentication Service” under in Chapter 5

of the ProCurve Secure Access 700wl Series Management and Configuration

Guide (December 2005), for a more detailed discussion of the steps for

configuring this authentication method.

HTTP Proxy Configuration per Access

Policy

The ProCurve Secure Access 700wl Series provides an internal HTTP proxy

service, and optionally allows the use of an external HTTP Proxy server to

handle HTTP traffic traveling through the 700wl Series system.

■ In software version 4.1 and earlier, a single external HTTP Proxy

server could be configured on an Access Controller.

■ In software version 4.4, external HTTP proxy servers can be config-

ured within individual Access Policies to handle HTTP traffic from

users affected by those Access Policies.

There are advantages and disadvantages to each of these methods of config-

uring and using HTTP proxy services:

■ Using the internal HTTP Proxy server allows HTTP filters to be set

within an Access Policy to filter the HTTP traffic on the ports being

monitored. Client browsers do not need to be configured for the proxy

server, and HTTP traffic can be redirected to the system HTTP pages

such as the Logon page.

However, the internal HTTP proxy server is relatively light-weight, not

compliant with HTTP 1.1, and is not capable of providing high-end perfor-

mance.

■ When an external HTTP proxy server is configured at the Access

Controller, HTTP traffic is passed to the external proxy server, but

only after it had first been filtered by the internal Proxy Server. Thus

this method retains both the advantages and disadvantages of the

internal proxy server—client browsers do not require proxy configu-