On Fri, May 18, 2018 at 4:07 PM, Poul-Henning Kamp wrote:
>
> In message
>
> , Dridi Boukelmoune writes:
>
>>> vmod.tell [VCL_PATTERN:]VMODNAME arguments [...]
>
>>Can we also pass a nonce to the VMOD? So that "global" actions can be
>>skipped once done when a VMOD like xkey is
In message
, Dridi Boukelmoune writes:
>> vmod.tell [VCL_PATTERN:]VMODNAME arguments [...]
>Can we also pass a nonce to the VMOD? So that "global" actions can be
>skipped once done when a VMOD like xkey is targeted with a VCL pattern
>matching more than once.
You are entirely i
On Fri, May 18, 2018 at 11:30 AM, Poul-Henning Kamp wrote:
>
> In message , Geoff Simmons
> write
> s:
>
>>> vmod.tell somevcl::somevmod "bla bla bla"
>
> I looked a bit at this.
>
> There is a hurt of locking issues for VMOD writers trying to do
> anything smart, but trivial stuff
In message , Geoff Simmons write
s:
>> vmod.tell somevcl::somevmod "bla bla bla"
I looked a bit at this.
There is a hurt of locking issues for VMOD writers trying to do
anything smart, but trivial stuff like setting global options for
the VMOD etc, shouldn't cause trouble.
VCC wi
