Cisco Cisco Web Security Appliance S170 사용자 가이드
4-14
AsyncOS 9.0 for Cisco Web Security Appliances User Guide
Chapter 4 Intercepting Web Requests
FTP Proxy Services
http://server_address[.domain][:port][/filename] | http://WSAHostname[/filename]
where WSAHostname is the hostname value configured when hosting the PAC file on a Web Security
appliance. Otherwise the URL format will depend on the storage location and, in some cases, on the client.
appliance. Otherwise the URL format will depend on the storage location and, in some cases, on the client.
Related Topics
•
.
Detecting the PAC File Automatically in Clients
Step 1
Create a PAC file called
wpad.dat
and publish it to a web server or Web Security appliance (the file must
be placed in a web server’s root folder if you intend using WPAD with DNS).
Step 2
Configure the web server to set up
.dat
files with the following MIME type:
application/x-ns-proxy-autoconfig
Note
A Web Security appliance does this for you automatically.
Step 3
To support DNS lookup, create an internally resolvable DNS name beginning with ‘
wpad
’ (for example,
wpad.example.com
) and associate it with the IP address of the server hosting the
wpad.dat
file.
Step 4
To support DHCP lookup, configure your DHCP server’s option 252 with the url of the wpad.dat file
location (for example: “
location (for example: “
http://wpad.example.com/wpad.dat
”). The URL can use any valid host
address, including an IP address, and does not require a specific DNS entry.
Related Topics
•
.
•
.
FTP Proxy Services
•
•
Overview of FTP Proxy Services
The web proxy can intercept two types of FTP requests:
•
Native FTP. Native FTP requests are generated by dedicated FTP clients (or by browsers using
built-in FTP clients). Requires the FTP proxy.
built-in FTP clients). Requires the FTP proxy.
•
FTP over HTTP. Browsers sometimes encode FTP requests inside HTTP requests, rather than using
native FTP. Does not require the FTP proxy.
native FTP. Does not require the FTP proxy.