okay i see https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/systemd-cron_2.3.0-1.rbuild.log.gz requested, but it's not marked as gzip-encoded in the reply, there's no Content-Encoding at all lol
okay on my brother's computer (and another tester's) it replies "content-encoding: gzip, gzip", and it renders correctly but on my and father's it removes c-e and sends "X-Content-Encoding-Over-Network: gzip" instead. why? what does this mean?
and of course webmaster@ fucking bounces
okay, apparently c-e: gzip, gzip means gzip(gzip("plain")), so the reply is nominally correct, but lynx and ESET eat shit on this
@nabijaczleweli that sounds incredibly like antivirus software with web scanning
@grawity you know what...... both affected machines are running ESET, you may well be a genius
on a third machine (no ESET) it doesn't happen under curl but does under lynx (but im not discounting lynx simply not understanding content-encoding)
@grawity yep, disabling HTTP(S) scanning in ESET fixes this. incredible product
@nabijaczleweli could be worse, I've had to troubleshoot a student's inability to login when BitDefender's HTTP scanning was outright cutting off the entire POST body in SAML SSO before it reached the server