Fortinet 5.0 Patch 6 Configuring compression offloading

Fortinet 457 FortiWeb 5.0 Patch 6 Administration Guide

5. Click Create New.

A dialog appears.

6. Enable Host Status to require that the Host: field of the HTTP request match a protected

hosts entry in order to match the exclusion.

Also configure Host.

7. From the Host drop-down list, select which protected host entry that the Host: field of the

HTTP request must be in to match the exclusion.

This option is available only if Host Status is enabled.

8. In Request URL, type the exact URL of the page to use in the exclusion.

The URL must begin with a slash ( / ). The URL must not include the domain or IP address.

9. Click OK.

10.Include the exception in a compression or decompression policy (see “Configuring

compression offloading” on page 457 or “Configuring decompression to enable scanning &

rewriting” on page 460).

Configuring compression offloading

Most web servers can be configured to compress files when responding to a request.

Compressed files often reduce bandwidth, and can result in faster delivery time to clients.

(Modern browsers automatically decompress files before displaying the web pages.)

To successfully decompress and read the response, clients use the corresponding

decompression algorithm. Web servers include an HTTP header such as:

Content-Encoding: gzip

to indicate which algorithm was used to compress the HTTP body:

^_<8B>^H^H+h,M^@^Cimage.png^@<EC><FC>St<AE>K<D4><EF><8B><C6>^\1G<AC>

^Q<DB>

<U+0588>Fl۶m۶m۶m<DB>^Y<D1>N<E6><9C><DF>^<AB><B5>sq<CE><D5><D9><FB>b<

A5><B5>\<BC><EF><F3>T/<F5><AA><EA><BF>^?<F5>$DZR^X^F

^@^@^@?<80>,^@^@

(content truncated)

If want to gain the benefits that compression offers, but do not want to configure it on your web

servers, you can offload compression to FortiWeb instead.

If your web servers are starved for CPU cycles and RAM, offloading compression from your

web servers to FortiWeb can alleviate that bottleneck and improve performance.