On Fri, Feb 21, 2025 at 12:50:51PM +0100, Vincent Dechenaux wrote: > Hello, > > Oh thanks I'm glad to hear that!
You're welcome! > I hesitated to not do it globally and to do it per proxy, and I ended > up doing it globally to mimic "tune.comp.maxlevel". In fact the maxlevel is more about preserving the process' resources when using zlib, that's mostly why it's global. Same for the max-comp-cpu-usage or I don't exactly remember how it's called. > For my personal case I don't have that requirement, to have this > customisation level but that may be a good thing, yes. > > How would it look like? > Something like "compression minsize-req" and "compression minsize-res" ? > If so, what about "compression minsize" (not sure due to "algo" and > "type" being marked as legacy). That could work, yes. Indeed maybe prefer minsize-req and minsize-res so that we can choose based on the direction since we can even compress requests (some users in cloud environments paying for inter-area traffic are doing this to avoid paying for traffic twice for large uploads). > I could definitely send a new patch in that way. That would be great then! Do not hesitate to ask if you have doubts or questions. Thanks, Willy
