Web Security Manager can accelerate web server performance by caching static content and by compressing traffic to clients.
Depending on the mix of static and dynamic content caching of static documents can potentially improve performance by 300 - 500%.
Dynamic compression of transmission data potentially reduces bandwidth usage by 30 - 60% and thereby increases transfer rate by 50 - 100%.
HTTP compression reduces the transfer volume of static and dynamically generated web pages to approximately 1/3 of their original size proportionally speeds up the load time performance. This results in reduced traffic costs and in a better experience for the web site visitors.
The performance gain depends on the ratio to which content from the web server can be compressed, the size of the pages and the clients bandwidth.
Set the gzip compression level. Compression level is a trade off between CPU resources and Bandwidth consumption. High compression levels saves more bandwidth but consumes more CPU and vice versa.
The default compression level is set at 3 which is moderate but fast.
Compression of server responses is based on the response content type.
| Text
Check box |
If enabled, Web Security Manager will compress HTTP documents matching content-type Default: |
| Images
Check box |
If enabled, Web Security Manager will compress HTTP documents matching content-type Normally compression should not be enabled for images because in most cases they are already optimized/compressed for the web in which case compressing will be a waste of processing power. Default: |
| Application data
Check box |
If enabled, Web Security Manager will compress HTTP documents matching content-type Default: |
In some cases it may be necessary to specify exceptions from the compression by content type policy. Exceptions are defined using regular expressions matching the path segment of the requested URL (the URI).
| Enable Compression Exception by Regular Expression Check box |
If enabled Web Security Manager will match the URI using the regular expressions in the list. If there is a match compression will be disabled for the server response. |
| Regular expression |
Enter regular expressions matching part of or the entire path part you want to be excluded from compression. Note that unlike filter policy regular expressions the expression does not have to match the entire path from start to end. For example 'a' would be a valid regular expression matching all paths containing an 'a' while '\.class' would match all paths containing '.class'
|
TCP connection reuse dramatically improves response times for clients that have support for keep-alive by reusing socket connections already established.
| Enable keep-alive requests
Check box |
Enable / disable support for HTTP/1.1 keep-alive requests. If enabled, Web Security Manager will support keep-alive protocol specification as defined by HTTP/1.1 standard. Default: |
|||
| Max Keep-Alive requests
Input field |
Maximum number of requests on a kept alive connection. This setting limits the number of requests allowed per connection when Keep-Alive requests is enabled. If it is set to 0, unlimited requests will be allowed.
|
|||
| Max Keep-Alive timeout
Input field |
Max idle time on a keep alive connection. This value defines the number of seconds Web Security Manager will wait for a subsequent request before closing the connection.
|
![[Note]](images/note.png)