Description of problem:
Typically, remote content consists of large feeds in the XML format that can generally compress very well. As every scan that involves a rule that references remote content results in the content being downloaded, it creates a huge traffic load.
Version-Release number of selected component (if applicable):
oscap (at least) up to 1.3.4
Steps to Reproduce:
OpenSCAP doesn't advertise that it supports compression by means of the accept-encoding header.
OpenSCAP takes advantage of the underlying libcurl engine, and accepts gzip or deflate encoding.
Another PR which should make it easier to test this feature: https://github.com/OpenSCAP/openscap/pull/1561
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (openscap bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.