On Sun, Aug 1, 2021 at 6:48 AM Tim Rühsen <tim.rueh...@gmx.de> wrote: > > On 31.07.21 13:39, 積丹尼 Dan Jacobson wrote: > >>>>>> "TR" == Tim Rühsen <tim.rueh...@gmx.de> writes: > > TR> If you know that the server sends uncompressed content, you can > > TR> compress it yourself on-the-fly to avoid excessive disk space usage. > > TR> At least it works for single files: > > TR> wget -O- <URL> | gzip > radio.csv.gz > > > > That's nice but like https://github.com/curl/curl/issues/7516# I am > > interested in wget adding a new option, providing users a guaranteed way > > to prevent network usage charges caused by no way to tell wget "only > > agree to download if the server agrees to compress." > > > > I opened an issue for wget2 for discussion. I agree with the curl > maintainers PoV that this is a corner case and that implementing it may > come with a large code complexity. > > https://gitlab.com/gnuwget/wget2/-/issues/556
Another downside is side channel attacks when using compression with HTTPS. BREACH, CRIME and friends. (Sorry to comment here. GitLab auth does not work for me again). Jeff
