Hello, Oh thanks I'm glad to hear that!
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". 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). I could definitely send a new patch in that way. Thanks, Vincent Le ven. 21 févr. 2025 à 04:01, Willy Tarreau <w...@1wt.eu> a écrit : > > Hello Vincent, > > On Thu, Feb 20, 2025 at 11:26:04PM +0100, Vincent Dechenaux wrote: > > This option allows you to set the minimum payload size required for > > compression to be applied. > > This helps save CPU on both server and client sides when the payload does > > not need to be compressed. > > Thank you. I think that this is an excellent idea. Your patch looks super > clean and I'm fine with taking it as is. I'm just having a question before > doing so: shouldn't we do this in the proxy where compression is enabled > instead of fixing this globally ? I don't know the precise use case where > you faced this situation, but I'm wondering if there could be situation > where users would want to compress any size on some frontends, and only > large objects on high-speed links. I don't know if you have an opinion on > this. > > Thanks! > Willy
