Roundup Tracker - Issues

Message7301

Author rouilj
Recipients rouilj
Date 2021-07-26.01:54:56
Message-id <1627264496.48.0.550022015911.issue2551147@roundup.psfhosted.org>
In-reply-to
First pass in changeset:   6458:8f1b91756457

Had a couple of fixes to the tests afterward.

Changes from original description:

 404 pages may be compressed if > 100 bytes in size. No option to
   set size limit. Will see if anybody requests it.

 No option to choose which methods can be used for on the fly
   compression. Use of virtualenv and installing just the compression
   modules you want to use is suggested. Preferred order is hardcoded
   (first to last) zstd, brotli gzip.

 Admin/config settings are limited:
    turn on/off dynamic compression. Default on.
    enable/disable looking for precompressed static
        assets. Default off since admin needs to compress the
        assets. Default of off means there is no search penalty
        by default.

Any precompressed asset that can be handled by the client will
prevent on the fly compression of that asset. This happens even if
the on-the-fly compression is a better choice.

E.G. if the file foo.css.gzip exists, a request for @@file/foo.css
with brotli or gzip encoding will send the gzip encoding. It will
not upgrade to brotli encoding because a pre-compressed foo.css.br
does not exist.

If foo.css.gzip did not exist, foo.css would be served and brotli 
encoding would be done on the fly.

If the client can't handle gzip, foo.css would be served with brotli.

This way pure dynamic content can use brotli, but static assets can
use only the acceptable provided pre-compressed assets.

Marking as pending and if no updates in a couple of weeks will close.
History
Date User Action Args
2021-07-26 01:54:56rouiljsetmessageid: <1627264496.48.0.550022015911.issue2551147@roundup.psfhosted.org>
2021-07-26 01:54:56rouiljsetrecipients: + rouilj
2021-07-26 01:54:56rouiljlinkissue2551147 messages
2021-07-26 01:54:56rouiljcreate