According to our understanding of the documentation, the compress plugin should deliver requests for the content types configured as compressible to browsers that send the corresponding request header (Accept-Encoding: gzip) in compressed form without exception.
Using the access.log, we were able to determine that this is not the case, and that individual resources are delivered uncompressed. For this evaluation, we added the following fields to the log format and were able to determine that about 3% of requests to URLs ending in .js are currently delivered uncompressed to browsers that accept gzip:
%<{Accept-Encoding}cqh> %<{Content-Encoding}psh> %<{Content-Type}psh>
According to our compress.config all .js resources should be compressed:
compressible-content-type application/javascript*
compressible-content-type application/x-javascript*
compressible-content-type application/json*
We also noticed that some resources are sent to the requesting browser sometimes compressed and sometimes uncompressed.
=> What is the expected behavior for the compress plugin? Should all compressible resources be delivered only in compressed form if the compression is accepted by the browser? Or does the plugin act according to the best effort principle, so that it is to be expected that individual resources are delivered uncompressed?
We are currently using version 8.1.3 of Apache Traffic Server on RHEL 7.9.
According to our understanding of the documentation, the compress plugin should deliver requests for the content types configured as compressible to browsers that send the corresponding request header (Accept-Encoding: gzip) in compressed form without exception.
Using the access.log, we were able to determine that this is not the case, and that individual resources are delivered uncompressed. For this evaluation, we added the following fields to the log format and were able to determine that about 3% of requests to URLs ending in .js are currently delivered uncompressed to browsers that accept gzip:
%<{Accept-Encoding}cqh> %<{Content-Encoding}psh> %<{Content-Type}psh>According to our compress.config all .js resources should be compressed:
We also noticed that some resources are sent to the requesting browser sometimes compressed and sometimes uncompressed.
=> What is the expected behavior for the compress plugin? Should all compressible resources be delivered only in compressed form if the compression is accepted by the browser? Or does the plugin act according to the best effort principle, so that it is to be expected that individual resources are delivered uncompressed?
We are currently using version 8.1.3 of Apache Traffic Server on RHEL 7.9.