Hi,
When implementing in VCL complex logic (not necessarily related with caching
contents -e.g. access control, rate limiting, etc.-) varnishtest is a powerful
tool to automate VCL testing. These type of tests sometimes are complex and
they are not easy to split in smaller pieces.
In some extr
On Thu, Sep 10, 2015 at 1:26 PM, Carlos Abalde wrote:
> Hi,
>
> When implementing in VCL complex logic (not necessarily related with caching
> contents -e.g. access control, rate limiting, etc.-) varnishtest is a
> powerful tool to automate VCL testing. These type of tests sometimes are
> compl
In message
, Dridi Boukelmoune writes:
>On Thu, Sep 10, 2015 at 1:26 PM, Carlos Abalde wrote:
>> Hi,
>>
>> When implementing in VCL complex logic (not necessarily related with caching
>> contents -e.g. access control, rate limiting, etc.-) varnishtest is a
>> powerful tool to automate
In message
, Guillaume Quintard writes:
Guillaume,
I'm very happy you did this, and I need to make up my mind about
the Makefile.phk stuffs fate.
However, I want to concentrate on getting 4.1 out, so can you come
back with this again once we have shoved that out the door ?
--
Poul-He
Of course. I'll keep a github branch rebased on master to track
changes happening in the meantime.
--
Guillaume Quintard
On Thu, Sep 10, 2015 at 3:07 PM, Poul-Henning Kamp wrote:
>
> In message
>
> , Guillaume Quintard writes:
>
> Guillaume,
>
> I'm very happy you did this, and I need
> On 10 Sep 2015, at 15:00, Poul-Henning Kamp wrote:
>
>
> In message
>
> , Dridi Boukelmoune writes:
>> On Thu, Sep 10, 2015 at 1:26 PM, Carlos Abalde
>> wrote:
>>> Hi,
>>>
>>> When implementing in VCL complex logic (not necessarily related with
>>> caching contents -e.g. access
Hi,
This is Varnish 4.1 material.
I have finally done and tested the changes we had decided to make
during the last VDD:
- removing the USE event
- allowing VMODs to fail a WARM event
- VCL reference counting for VMODs
- relaxing the "cold" restrictions on cooling VCLs
I have found and fixed mor
