Byte caching.
Byte caching improves caching by accelerating the transfer of similar, but not identical content.
Byte caching reduces the amount of data crossing the WAN when multiple different emails with the same or similar attachments or different versions of an attachment are downloaded from a corporate email server to different locations over the WAN.
Byte caching breaks large units of application data, such as email attachments or file downloads, into smaller chunks of data.
Each chunk of data is labeled with a hash, and chunks with their respective hashes are stored in a database on the local FortiGate.
When a remote user requests a file, WAN optimization sends the hashes, rather than the actual data.
The FortiGate unit at the other end of the WAN tunnel reassembles the data from its own hash database, only downloading the chunks it is missing.
Deduplication, or the process of eliminating duplicate data, will reduce space consumption.
Byte caching is not application specific, and assists by accelerating all protocols supported by WAN optimization.
Web caching.
WAN optimization reduces download times of content from central files repositories through web caching.
FortiOS Web caching stores remote files and web pages on local FortiGates for easy local access to commonly accessed files.
There is little impact on the WAN, resulting in reduced latency for those requesting the files.
In addition, web caching also recognizes requests for Windows or MS Office updates, and downloads the new update file in the background.
Once downloaded to the cache, the new update file is available to all users, and all subsequent requests for this update are rapidly downloaded from the cache.
Traffic shaping.
Controls data flow for specific applications, giving administrators the flexibility to choose which applications take precedence over the WAN.
A common use case of traffic shaping prevents one protocol or application from flooding a link over other protocols deemed more important by the administrator.
SSL acceleration.
SSL is used by many organizations to keep WAN communications private.
WAN Optimization boosts SSL acceleration properties of FortiGate FortiASIC hardware by accelerating SSL traffic across the WAN.
The FortiGate unit handles SSL encryption/decryption for corporate servers providing SSL encrypted connections over the WAN.
Explicit web proxy server.
Allows users on the internal network to browse the Internet through the explicit web proxy server.
Explicit FTP proxy server.
Allows users on the internal network to access FTP servers through the explicit FTP proxy server.
Reverse proxy.
The web and FTP proxies can be configured to protect access to web or FTP servers that are behind the FortiGate using a reverse proxy configuration.
Reverse proxies retrieve resources on behalf of a client from one or more servers.
These resources are then returned to the client as if they originated from the proxy server.
WCCP.
The Web Cache Communication Protocol (WCCP) allows to offload web caching to redundant web caching servers.
This traffic redirection helps to improve response time and optimize network resource usage.
WAN optimization and HA.
Configure WAN optimization on a FortiGate HA cluster.
The recommended HA configuration for WAN optimization is active-passive mode.
Also, when the cluster is operating, all WAN optimization sessions are processed by the primary unit only.
Even if the cluster is operating in active-active mode, HA does not load-balance WAN optimization sessions.
HA also does not support WAN optimization session failover.
Configuring an explicit proxy with WAN optimization web caching.
For this configuration, all units on the wireless network will be required to connect to the proxy at port 8080 before it can browse the Internet.
WAN Optimization web caching is added to reduce the amount of Internet bandwidth used and improve web browsing performance.
Enabling WAN optimization and configuring the explicit web proxy for the wireless interface.
Go to System -> Feature Visibility and ensure that Explicit Proxy is enabled.
1) To make WAN optimization and web caching settings available from the GUI, enter the following CLI command:
# config system settings
set gui-wanopt-cache enable
end
2) Go to Network -> Interfaces, edit the wireless interface and select' Enable Explicit Web Proxy'.
3) Go to Network > Explicit Proxy. Enable Explicit Web Proxy. Make sure that Default Firewall Policy Action is set to Deny.
Adding an explicit web proxy policy.
1) Go to Policy & Objects -> Proxy Policy and create a new policy.
2) Set Proxy Type to Explicit Web, the outgoing interface to the Internet-facing interface, and the remaining fields as required.
Configuring units on the wireless network to use the web proxy.
To use the web proxy, all units on the wireless network have to be configured to use the explicit proxy server.
The IP address of the server is the IP address of the FortiGate’s wireless interface (for example, 10.10.80.1) and the port is 8080.
Some browsers have to be configured to use the unit's proxy settings.
1) For Windows 10, select the Windows start-icon and select Network Connections. Select Proxy and configure the proxy settings.
2) For Windows Vista/7/8, open Internet Properties. Go to Connections -> LAN Settings and enable and configure the Proxy Server.
3) For Mac OS X, got to System Preferences -> Network -> Wi-Fi -> Advanced -> Proxies, select Web Proxy (HTTP) and configure the proxy settings.
4) For iOS, go to Settings -> Wi-Fi, edit the wireless network. Scroll down to HTTP PROXY, select Manual, and configure the proxy settings.
5) For Android, in WiFi network connection settings, edit the wireless network. Select Show advanced options, configure a Manual proxy and enter the proxy settings.
Force HTTP and HTTPS traffic to use the web proxy.
Block HTTP and HTTPS access to the Internet from the wireless network so that the only path to the Internet is through the explicit proxy.
Edit or delete policies that allows HTTP or HTTPS access.
Add also a policy to the top of the list that Denies HTTP and HTTPS traffic.