Index | Thread | Search

From:
Job Snijders <job@sobornost.net>
Subject:
Re: rpki-client: indicate instances of suboptimal HTTP content encoding
To:
Theo Buehler <tb@theobuehler.org>, tech@openbsd.org
Date:
Wed, 11 Jun 2025 09:44:10 +0000

Download raw body.

Thread
On Wed, Jun 11, 2025 at 06:11:31AM +0200, Claudio Jeker wrote:
> I really would prefer if we did not add more log output like this.
> Both with and without -v the noise from rpki-client is too high.

I disagree, it took me far too many hours to discover that RIPE NCC's
RRDP servers don't have gzip compression enabled. :-)

The warning already is gated behind the 'verbose' command line option, the
warning shows less than a handful of times with an empty cachedir, and only
zero or one times for subsequent runs with a warm cache. In other words, the
warning only appears for egregious waste of bandwidth. I need something simple
(like this) to illustrate inefficiency and quickly test with publication point
operators.

> If you really want something I would suggest we track the number of bytes
> recevied (before and after decompression) to the repo stats.

If you have the cycles to additionally expose more detailed info like you
suggest in the openmetrics output that would be welcomed.

Is the patch correct?

Kind regards,

Job