Thank you Dridi
—
Vlad Rusu
Cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
> On 25 May 2020, at 16:34, Dridi Boukelmoune wrote:
>
> On Mon, May 25, 2020 at 1:19 PM Vlad Rusu wrote:
>>
>> Hi all,
>>
>> A question for the maintainer
I see version 6 only. Any reason to believe this won’t
work with varnish cache version 4.1.x?
I know.. I should upgrade. But till then..
Appreciate your support.
Thanks,
—
Vlad Rusu
Cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
___
I appreciate Guillaume’s diplomacy :)
Your issue (one of them at least) is that in your cascaded varnish setup
the hash key of the cached url, in both varnish storages, is the one you
use to originally access the asset. Your vcl hash routine might also be a
custom one.. that would be the next
templating and not
by trying to access ENV directly from the the backends VCL. I’m saying this
having a proper SDLC in mind.
Of course, dynamic backends and all other options Guillaume and
Paul-Henning have mentioned are solid.
Vlad Rusu
On Tue, 10 Sep 2019 at 22:14, Hugues Alary wrote
Hi guys,
https://www.varnish-cache.org/trac/wiki/Future_ESI
<https://www.varnish-cache.org/trac/wiki/Future_ESI> — is the "ESI 304
handling" bit addressed? I am seeing this behaviour so I’d assume it isn’t.
Are the bits mentioned there getting some traction anytime soon? :)
Of course :)
Thanks!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
> On 21 Feb 2017, at 10:09, Guillaume Quintard <guilla...@varnish-software.com>
> wrote:
>
> Hello Vlad,
>
> Normally, varnish is configured
ss%00"
- Hash "444%00"
- Hash “www…..com%00"
Thanks!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
> On 21 Feb 2017, at 09:58, Vlad Rusu <vlad.r...@lola.tech> wrote:
>
> Thanks a lot!
>
Thanks a lot!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
> On 21 Feb 2017, at 09:57, Geoff Simmons <ge...@uplex.de> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 02/21/2017 08:46 AM, Vla
se std to log or various other techniques, but am interested
in seeing the Hash like we used to with Varnish 3.
Any hints?
Thanks a lot!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
___
varnish-
d here..
Thanks for your hard work on this cool product guys!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
> On 06 Jan 2017, at 15:07, Dridi Boukelmoune <dr...@varni.sh> wrote:
>
> On Fri, Jan 6, 2017 at 10:28 AM, Vlad Rusu
think it makes sense.
Each backend sends gzipped data back to Varnish and each client requests for
gzipped data from Varnish..
Thanks!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
___
varnish-
ective privileges
to normal user mode when not doing operations needing special access.
The Varnish worker child should now be run as a separate vcache user."
Thanks!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
> On 22 Nov 2016,
9:32 0:00 \_
/usr/sbin/varnishd -P /var/run/varnish.pid -f /etc/varnish/default.vcl -a :6081
-T 127.0.0.1:6082 -S /etc/varnish/secret -s malloc,256M
===
Thanks!
--
Vlad Rusu
skypeid: rusu.h.vlad | cell: +40758066019
Lola Tech | lola.tech <https://lola.tech/>
___
13 matches
Mail list logo