To fine-tune OLS, an explanation is needed. With dynamic GZIP compression, everything is relatively clear, but with static compression, no.
Do I understand the compression logic correctly, if, for example, only "Auto Update Static File" and "GZIP Compression Level (Static File)" are enabled?
1. User 1 visits the site, Gzip creates files in the "Static Cache Directory" and when user 2 visits, the server gives him these compressed files?
2. If the file has changed, "Auto Update Static File" creates a new file and when the user visits the site, OLS gives the new compressed file?
If you additionally enable "Brotli Compression Level (Static File)", then the algorithm will be as follows:
1. User 1 visits the site, Brotli (has priority over Gzip) creates files in the "Static Cache Directory" and when user 2 visits, the server gives him these compressed files or the Brotli module re-compresses the files with each request?
2. Does "Static Cache Directory" work with Brotli?
These points are not entirely clear.
Do I understand the compression logic correctly, if, for example, only "Auto Update Static File" and "GZIP Compression Level (Static File)" are enabled?
1. User 1 visits the site, Gzip creates files in the "Static Cache Directory" and when user 2 visits, the server gives him these compressed files?
2. If the file has changed, "Auto Update Static File" creates a new file and when the user visits the site, OLS gives the new compressed file?
If you additionally enable "Brotli Compression Level (Static File)", then the algorithm will be as follows:
1. User 1 visits the site, Brotli (has priority over Gzip) creates files in the "Static Cache Directory" and when user 2 visits, the server gives him these compressed files or the Brotli module re-compresses the files with each request?
2. Does "Static Cache Directory" work with Brotli?
These points are not entirely clear.