retty straightforward.
--
Thomas Lecomte | Sysadmin @ Virtual Expo
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
say wether it is able to cope
with more than 1000 req/s without increasing the CPU load.
I only implemented the bindings we needed, that's why I don't provide
full bindings to the whole library yet. I can add some if you need
them.
Thanks,
--
Thomas Lec
could enable a client to saturate
the cache by filling it until exhaustion.
--
Thomas Lecomte / Sysadmin
+33 4 86 13 48 65 / Virtual Expo, Marseille
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/ma
nique object is computed in vcl_hash,
and by default, includes req.http.host (the HTTP Host: header sent by
the client). You don't have to modify something since it's not the
Host header sent to the backend that is being hashed, but the one sent
from the client to varnish.
Hope this helps,
--
Th
hd runs). Might it not be a permissions problem for you?
--
Thomas Lecomte / Sysadmin / Virtual Expo
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
unk/reference/varnish-cli.html#vcl-discard-configname-label
--
Thomas Lecomte / Sysadmin / Virtual Expo
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
ith -F and %{VCL_Log:MR} plus
%{Varnish:handling} to log the match rule and the handling of the
request (miss, hit, pipe, pass, whatever). You will have to parse this
output yourself to compute a ratio.
--
Thomas Lecomte / Virtual Expo
___
varnish-misc m
arnishncsa manpage).
--
Thomas Lecomte / Virtual Expo
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
aders and later asking for their
> content?
Hello,
Unfortunately, since v4, you can't test req.backend_hint.
I had to define a custom HTTP header every time I set req.backend_hint
to keep track of it.
--
Thomas Lecomte / Virtual Expo
___
varnish
the request
only one time.
Regards,
--
Thomas Lecomte
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
to do this? A
lot of what I've found online is not for V4 so it's not working. Thanks!
Have you checked out this page?
https://www.varnish-cache.org/trac/wiki/VCLExampleCacheCookies
It seems to be Varnish 4-compliant.
Hope this helps,
--
Thomas Lecomte
be cached if
it contains a Set-Cookie HTTP header.
You might want to take care of these cases yourself if you want to
cache those kind of pages, instead of leaving it to the default VCL
implementation.
Regards,
--
Thomas Lecomte
___
varnish-misc mailing
of every single object you want to purge from the cache. I don't think
you can purge multiple objects at once, unlike with bans.
If I am wrong, I would love to be corrected because I had the very
same issue and had to went with bans instead :-)
/Thomas
--
Thomas Lecomte | Sysadmin
Virtual Expo
if a single client makes
multiple calls to the API.
I think a workaround could be to use a fake cached object using a static
hash, and then rewriting the response in vcl_deliver with the actual
JSON.
Never done that though - just an idea.
Regards,
--
Thomas Lecomte / Administrateur Système Réseau
for further
requests.
--
Thomas Lecomte
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
On Thu, Apr 17, 2014 at 04:38:58PM +0200, Anton Kornexl wrote:
Hello,
how do i find out why varnish cache gets cleared randomly.
Maybe have a look at the n_lru_nuked metric. If you cache gets full,
varnish will start nuking the least used objects to make room for the
new ones.
--
Thomas
could compare the inodes using ls -i on the visible _.vsm
against the one shown by lsof on the varnish process.
--
Thomas Lecomte / +33 4 86 13 48 65
Sysadmin / Virtual Expo / Marseille
___
varnish-misc mailing list
varnish-misc@varnish-cache.org
https
it the other way?
i.e.:
if (req.request == PURGE ) {
if (client.ip ~ purge) {
return (lookup);
}
error 403 Forbidden;
}
Regards,
--
Thomas Lecomte / +33 4 86 13 48 65
Sysadmin / Virtual Expo / Marseille
___
varnish
18 matches
Mail list logo