System administrators may want to enable Hypertext Transfer Protocol (HTTP) Compression (Gzip) on their Apache Tomcat HTTP Connectors. With HTTP compression, users can limit the amount of bandwidth distributed between the Strategy Web Server and the Strategy Web client machine. In particular, system administrators may wish to enable HTTP compression if the connection speed between the Strategy Web server and the client machine is particularly slow. With HTTP compression, the web files are compressed before they are shipped over the Internet. Once the files reach the client's machine, they are decompressed by the client's machine.
However, there are a few disadvantages to using file compression. First, the Web Server (Tomcat) will spend CPU time to compress the files before they are sent. Second, the client machine will spend time decompressing the files. In general, these two factors will not greatly impact the system because the amount of CPU time required is fairly low and since most current web browsers are designed to account for file compression.
Enabling HTTP Compression
Note: For more information about the Tomcat HTTP Connector and what options there are regarding compression, refer to the Apache Tomcat Configuration Reference:
https://tomcat.apache.org/tomcat-7.0-doc/config/http.html
Additionally, this issue may persists in 10.4.8. If this is the case, please upgrade to Strategy 2019 or later.
Third Party Software Installation:
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.