Rubén Romero

@glensc I meant adding it to the official Varnish Cache extras list: https://varnish-cache.org/extras/

https://github.com/KristianLyng/varnishfoo/pull/31 or similar should allow you to close this issue.

I approve. On Wed, Oct 20, 2021, 15:50 Max ***@***.***> wrote: > To all contributors of this repository, could you please give your > approval or disapproval of the recent...

Hello, I thought I'd chip in. We (Varnish Software) have made a new one from scratch (sorry Nand) for V4. As soon as it hits github I will copy you...

Hello, You will have to thank Dag who made it. He just published it online: https://github.com/daghf/libvmod-vsthrottle As mentioned before, it is Varnish 4.0 only. On Thu, Apr 24, 2014 at...

Varnish modules (VMODs) are only available from Varnish 3.0 and on. So by definition this is not available in earlier versions. It is now issue #4 and has been sent...

No, you cannot automate the whole 3>4 conversion process. That's why it's not supported. As with everything Varnish, make sure you understand what's going on. In this specific case use...

Tanaka, Eduardo, There were some discussions (including PHK) about this under VUG5, but I am not sure what the conclusion was. And, I am still too excited to have an...

It seems you got it right now, at least :-) http://blog.xcir.net/index.php/2012/06/to-parsing-the-postget-request-and-cookie-header-of-varnish-vmod-parsereq/ https://github.com/xcir/libvmod-parsereq How does this relate to the Sec.VCL + Varnish Firewall Roadmap/To-Do list?

I could arrange for a Roadmap/To-Do list update if you seem it relevant. Let me know.