Comment 1 for bug 1907544

IMHO we should not change the collection logic in order to accommodate what seems to be a hosting configuration issue. Instead this should be addressed at RDO logserver config.

In fact I would say that we should not even pre-compress the files, compression at rest is something that should be done transparently by log server. It is a known issue, raised several times during the last years and every time we were asked to implement workarounds like these which cause more problem than resolving.

For example the already existing upload-logs-s3 role already uploads files while compressing them on the fly and keeping them compressed at rest on S3. Still, the files are served correctly to the user.

The user never sees a ".gz" url, it just grabs the file and the server (S3) will serve that file using correct headers and a compresses stream.

That is a low-overhead and low-cost solution that is transparent. maybe we should just switch to use S3 until RDO is upgraded.