Re: Caching Modified URLs by Varnish instead of the original requested URL

On 9/1/23 16:58, Guillaume Quintard wrote: - vmod-re is based on libpcre2 - vmod-re2 is based on libre2 Correct? Correct. It used to be the case that libvmod-re only used the internal VRE interface. So the VMOD was using whatever Varnish used, so to speak, which happened to be pcre. But

Re: Caching Modified URLs by Varnish instead of the original requested URL

Sorry, I get nerdy about this subject and can't help following up. I said: - pcre2 regex matching is generally faster than re2 matching. The point of re2 regexen is that matches won't go into catastrophic backtracking on pathological cases. Should have mentioned that pcre2 is even better at

Re: Caching Modified URLs by Varnish instead of the original requested URL

On 8/31/23 22:06, Guillaume Quintard wrote: Other options include vmod_querystring (Dridi might possibly be of assistance on this topic) and vmod_urlplus

Re: Purging cached std.fileread() contents

On 6/15/23 18:57, Justin Lloyd wrote: The documentation for std.fileread() says it is cached indefinitely, so how do I get Varnish to re-read the file when it gets updated without having to restart Varnish? "Cached indefinitely" means just what it says. The VMOD saves the file contents in

Re: Need Assistance in Configuring Varnish to Retain and Ignore Unique Parameter in Request URL while caching

On 6/1/23 03:47, Uday Kumar wrote: Our Requirements: [...] 3. Allowed Characters are Alphanumeric which are *URL safe* [can be lowercase, uppercase in case of alphabets] [...] This time you didn't mention a requirement of exactly 20 characters. If that's not strictly required, it's worth

Re: Need Assistance in Configuring Varnish to Retain and Ignore Unique Parameter in Request URL while caching

On 5/31/23 20:06, Uday Kumar wrote: We would like to configure varnish to create unique parameter such that its value should be of 20 characters (alphanumeric characters that are URL safe). I have used VMOD uuid to set unique values in each request: https://github.com/otto-de/libvmod-uuid

Re: TTL <=0 ?

On 9/27/22 15:07, Johan Hendriks wrote: Hello all, varnish tells me that the TTL is smaller or equal to 0, but looking at the response headers that is not the case as the BerespHeader has  Expires: Wed, 27 Sep 2023 12:23:11 GMT which is in 2023! -   Begin  bereq 8203147 pass The

Re: Confusion about LTS versions. Any comprehensive documentation regarding everything LTS?

Batanun B writes: Any info on upcoming LTS versions? I'm specifically interested in new non-minor versions, like 6.6 or 7.0. This thread has helped me notice that some things I knew about LTS don't appear to be stated very obviously in the docs. LTS versions have been at an N.M.x version for

Re: Docker images: Alpine and new architecture support

On 8/6/21 02:59, Guillaume Quintard wrote: > > In short, all images are now supported on amd64, arm32v7, arm64v8, i386, > ppc64le, and s390x. And on top of this, the "fresh" tags are also > accessible with an "-alpine" suffix (fresh-alpine, 6.6.1-alpine, etc.). Guillaume this is good news,

Re: Best practice for caching scenario with different backend servers but same content

On 8/9/21 14:49, Geoff Simmons wrote: > > A hash algorithm computes a number h(b) for a backend b, ... Sorry, this should have been more like h(bereq), meaning that the number is computed from features of the request. From that you get to the choice of a backend. The Varnish hash directo

Re: Best practice for caching scenario with different backend servers but same content

Hello, The best way to answer these questions is to start with the last one: On 8/9/21 10:50, Hamidreza Hosseini wrote: > > 6. conceptual question: > > 1.What's the exact difference between hash and shard directive and when > should we use which one? > the Doc says when the backend changes

Re: varnish eats all RAM

On 4/29/21 17:21, Marco Dickert - evolver group wrote: > > we have a weird problem with one of our varnish instances running on debian > buster. The problem is, that varnish consumes all RAM over time and does not > free it again. Just a hunch, but this is reminiscent of problems that I've seen

Re: Detect request coalescing?

On 7/30/20 21:28, Batanun B wrote: > Just a quick question that I wasn't able to find any information on > using regular google searches. Is it possible to detect request > coalescing somehow? Meaning that, when looking at the response headers, > can I somehow see that the request had to wait for

Re: Transparent hugepages on RHEL8

On 5/24/20 01:29, info+varn...@shee.org wrote: > This notes > > https://varnish-cache.org/docs/trunk/installation/platformnotes.html > > has a comment about "Transparent hugepages". > > Does this still apply to EL8? That's a good heads-up that those docs need to be updated -- they refer to

Re: Varnishncsa Random Log Sampling ?

On 3/2/20 12:13, Yassine Aouadi wrote: > > Is there Any way to go further with varnishncsa and perform and random > sampling of my access logs ? for example write only 10 % of access logs I've done that with log queries in the varnishncsa or varnishlog command line. For example, this query

Re: Caching a resource after specific number of requests

On 12/5/19 11:24, Dridi Boukelmoune wrote: > On Tue, Dec 3, 2019 at 6:04 PM al sefid wrote: >> >> Is there any functionality like proxy_cache_min_uses in the >> Varnish cache that caches a resource after specific number of >> requests to that resource? > > Varnish is not capable of doing that by

Re: Wrong VMOD_ABI_Version in 6.0.5 src rpm

On 11/27/19 17:27, Guillaume Quintard wrote: >> >> https://packagecloud.io/varnishcache/varnish60lts/packages/el/7/varnish-6.0.5-1.el7.src.rpm Note version 6.0.5. >> contains a wrong VMOD_ABI_Version define. >> >> #define VMOD_ABI_Version "Varnish 6.0.4 >>

Re: Usage of the Shard director ( rampup period )

On 11/14/19 11:43, Yiannis Karayiannidis wrote: > > sub vcl_init { > new dir_b = directors.shard(); > dir_b .add_backend(wb3); > dir_b .add_backend(wb2); > dir_b.add_backend(wb1); > dir_b .set_rampup(2m); >

Re: base64 blob.decode() default error handling

On 11/4/19 03:32, pyunyh wrote: > Hi, > > In order to validate client supplied base64 encoded string I have a > VCL something like the following. > > if (blob.length(blob.decode(BASE64, 0, req.http.Sec-WebSocket-Key)) > != 16) { > return (synth(400, "Bad Request")); >

Re: How to send only whitelisted http headers to backend?

On 10/15/19 16:21, Jeff Potter wrote: > > This seems like an easy task, but I haven’t been able to figure out > how to do it or find any posts online. Is there a way to only send > certain headers to a backend? > > I.e. in our application, we know we only need X-Forwarded-For and > Cookie

Re: Migration from 4.1 vcl

On 10/9/19 18:03, Cosimo Streppone wrote: > > What I meant was if there's any vmod interface/api change between 4.1 and 6.0 > that could break third party vmod code, if that makes any sense. Yes. With just about every new version of Varnish, there's always something. It may be not be much for

Re: Reg: global variable in vcl

On 5/17/19 16:29, Nils Goroll wrote: > > * with respect to global variables and types: > > On 17/05/2019 13:09, Geoff Simmons wrote: > > VMOD var supports global variables for the STRING, INT and REAL types, > > not that I would be aware, to my knowledge th

Re: Reg: global variable in vcl

On 5/16/19 10:41, Hardik wrote: > > Does I have to take care something while using this vmod ? Because first > time going to use and also not getting any information about this. That's a very generic question. Do you have something specific in mind? objvar is actually a bundle of four VMODs,

Re: Reg: global variable in vcl

On 5/15/19 13:20, Hardik wrote: > > -can you point out exact path/location I can checkout and use this vmod, if > below path is not correct. ( I am using varnish 6.1 ) > https://gitlab.com/uplex/varnish/varnish-objvar/tree/6.1 That's a branch, you'll want to check out the 6.1

Re: Reg: exact field for response time

On 3/20/19 07:14, Hardik wrote: > > what time should give to customer as a response time? Is it 2nd field(Total > round trip time) or 3rd field(only response time after processed fetched > content) ? >Timestamp Resp: 1501601912.806787* 0.048125* *0.37* > > Reason of asking this

Re: Reg: exact field for response time

On 3/18/19 12:09, Hardik wrote: > > *varnish 6.1* > Timestamp Resp: 1501601912.806787 0.048125 *0.37* > > https://feryn.eu/blog/varnishlog-measure-varnish-cache-performance/#The_Timestamp_tag > > > -> Are both fields give same values, means same meaning or both are > different? In varnish

Re: Varnish error for failed backend

On 03/31/2018 02:36 PM, Danila Vershinin wrote: > > However, I’m also interested how can we distinguish backend errors > while using grace mode and failed probe. > > Suppose that you have configured grace mode and a health check > against homepage. And homepage fails with 500. > The backend is

Re: Varnish error for failed backend

On 03/31/2018 10:21 AM, Danila Vershinin wrote: > > If a constant PHP error occurs in the backend and there is no cache - > we see Backend fetch failed. [...] > ... it always takes time to explain to the clients that the Varnish > is not to blame ... Welcome to Varnish administration! Such is

Re: VCL 4.1 and beresp.backend.ip

On 03/29/2018 08:24 PM, Hugues Alary wrote: > > VCL 4.1 retired beresp.backend.ip. > > Is there any way in VCL 4.1 to get the IP Address of the backend used? No. There have been some thoughts about adding something for "get backend info" in a future version, which would expose the IP address

Re: vmod_header can be used in vcl_backend_fetch?

On 11/27/2017 01:04 PM, matrix wrote: > > According to varnishlog Bereq header are displayed but origin server > log, only Accept-Encoding: . > > - BereqHeaderAccept-Encoding: > - BereqHeaderAccept-Encoding: > > I would like to change Accept-Encoding Header to

Re: Value of builtin.vcl - vcl_recv on modern websites

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/12/2017 09:14 AM, Matthew Johnson wrote: > > Since Varnish 1.0 the builtin (or default) vcl_recv has had this > statement: if (req.http.Authorization || req.http.Cookie) { > > /* Not cacheable by default */ > > return (pass); > > } > > My

Re: Varnishlog. Get entries by XID

On 04/10/2017 03:18 PM, Danila Vershinin wrote: > > Say I have stumbled upon a "Backend Fetch Failed” page and that > gives me an XID. > > How do I easily query varnishlog for corresponding client and > backend requests? > > varnishlog -q “XID = 12345” doesn’t work It can be done you're

Re: Backend Fetch failed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 For problems like this, *always look for the FetchError entry in the backend logs*. > << BeReq>> 65547 [...] > - FetchError no backend connection - Timestamp Beresp: > 1491485655.912871 0.51 0.51 - Timestamp Error: >

Re: only cache Get and Head

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/17/2017 06:22 PM, Rodney Bizzell wrote: > I wanted to know what is the correct syntax to only want to cache > Get and Head if req.method. I used this and O got and error when I > checked the syntax. > > If (req.method ! = “GET” &&

Re: Varnish Panic

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/09/2017 10:15 PM, Yiannis Karayiannidis wrote: > > errno = 12 (Cannot allocate memory) > errno = 12 (Cannot allocate memory) Your system's memory was evidently full. Varnish attempted internal allocations, but they failed, and so the panics

Re: Varnish 4.1 - "Hash" in varnishlog is.. masked

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/21/2017 08:46 AM, Vlad Rusu wrote: > > Per https://varnish-cache.org/docs/4.1/reference/vsl.html, “Hash” > is masked by default. > > I am trying to use varnishlog to see the values added to the hash > and I just can’t find a way to show it.

Re: Support for If-None-Match header.

On 01/23/2017 01:56 PM, Jan Hugo Prins | BetterBe wrote: > > Somewhere I found an old Trac Wiki document that describes > something like this, but I can't figure out if this has been > implemented or not. > https://www.varnish-cache.org/trac/wiki/BackendConditionalRequests?version=8 That >

Re: FetchError :http first read error: EOF

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/21/2016 05:25 PM, Ayberk Kimsesiz wrote: > > I'm trying to solve this problem for a long time. I reset the > default.vcl settings, but it did not work. What is your > suggestion? > > * << BeReq>> 1277958 - FetchError http first

Re: 503 Backend fetch failed / (again)

On 11/21/2016 10:34 AM, Ayberk Kimsesiz wrote: > > Varnishlog: *FetchError http first read error: EOF* That's a first byte timeout. > *- FetchError http first read error: EOF* - BackendClose > 160 boot.default - Timestamp Beresp: 1479720457.535409 > 60.000158 60.88 -

Re: gzip not working in Varnish 4.1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/10/2016 07:52 PM, Miguel González wrote: > > My vcl backend_response is below, do I need to set somewhere > beresp.do_gzip = true even when I set it for varnishd? Yes. HTH, Geoff - -- ** * * UPLEX - Nils Goroll Systemoptimierung

Re: VSL Timeout and Varnishkafka

On 06/22/2016 01:04 PM, Luca Toscano wrote: > > Nice test that I found in the Varnish codebase (meant to trigger a > VSL timeout): > > https://github.com/varnishcache/varnish-cache/blob/4.1/bin/varnishtest/tests/r01762.vtc#L29 That's > probably your best bet. Otherwise, triggering VSL timeouts

Re: VSL Timeout and Varnishkafka

On 06/21/2016 07:27 PM, Luca Toscano wrote: > > - VSLtimeout - Endsynth The timeout (-T arg of the VSL tools) starts when the Begin tag for a transaction is read from shared memory, and ticks until the End tag is read for that transaction. If End is not encountered

Re: 503s for a non-cached host / Re: [SOLVED] Varnish stops waiting backend after 1 second

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/13/2016 09:48 AM, Garau Simone wrote: > > I still have an issue I can’t understand: I get some random 503 > from the backend where Varnish isn’t caching. After a couple of > refresh of the page is properly served. > > The Apache logs shows

Re: varnishadm backend.list missing IPs

On 02/05/2016 02:56 PM, Tim Little wrote: > > I have just upgraded to Varnish-4.1.1 from Varnish-4.0 and I have > noticed that `varnishadm backend.list` no longer displays the IP > address of the backend. > > We were using this to monitor the backends health in Nagios NRPE > check but this no

Re: Query regarding "http first read error: EOF" error in varnish

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/13/2016 10:49 AM, Jayanth Kalyanasundaram wrote: > Hello, > > We are currently using varnish 4.1.0 as a caching layer on top of a > few of our production servers, and from time to time we see a few > 503 errors in the varnish log with the

Re: Query regarding "http first read error: EOF" error in varnish

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/14/16 6:29 AM, Jayanth Kalyanasundaram wrote: > > Hey, like you said the issue only happens sometimes. But the > first_byte_timeout for all the backends is set to 300 seconds. > > [root@varnish ~]# sudo varnishadm "param.show

Re: Varnish3 and Munin : Hit rate exceeds 100%

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/12/2016 04:18 PM, maxe...@bothorel.net wrote: > > client_req 297721534.73 Client requests > received cache_hit 509536159.44 Cache hits > cache_hitpass 64796 0.76 Cache hits for pass

Re: Varnish 500 Backend Fetch Failed when varnish is started as service

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/30/15 10:27 AM, Debraj Manna wrote: > > I am new to varnish. Whenever I am trying to acess our backend via > varnish I am getting the below error:- Always look for the FetchError: > - FetchError no backend connection Varnish can't

Re: why i get response if it is a post request with pass?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/28/15 10:25 AM, יעקב ירמולובסקי wrote: > I'm using varnish 3 so I don't think that I have > vcl_backend_error. Right, but your VCL is evidently doing something in the form of error handling, since it reacted to the fetch error (which is seen

Re: why i get response if it is a post request with pass?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/28/15 11:30 AM, יעקב ירמולובסקי wrote: > But if I have the following in my vcl file: .first_byte_timeout = > 600s; .between_bytes_timeout = 600s; > > Doesn't varnish suppose to respect it? In that case it wasn't a first byte timeout.

Re: Why Body cannot be fetched?

On 12/15/2015 04:57 PM, Gonçalo Silva wrote: >> > < HTTP/1.1 200 OK < media-type: application/json;v=1 < > content-type: application/json; charset=utf-8 < cache-control: > no-cache < content-length: 698 < trailer: server-authorization < > transfer-encoding: chunked < accept-ranges: bytes < Date:

Re: Varnish and Docker

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/08/2015 10:33 PM, Lewis, Eric wrote: > > I'd like to solicit feedback from you and invite the Varnish > community to contribute to this effort. > > Most Dockerfiles install Varnish via a linux package manager, > which makes it impossible to

Re: can't log in or create new users on mediawiki

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 8/17/15 5:29 AM, Tim Dunphy wrote: I've setup my mediawiki behind varnish. Since doing that I am unable to either create new users or log into the wiki itself. I don't know how it works with mediawiki, but let's talk about regexen again.

Re: logical or statement failing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 8/16/15 8:00 PM, Tim Dunphy wrote: ^/?\?oa_social_login_source=custom$ ^\?oa_social_login_source=custom$ The '^' anchors the regex at the beginning of the string. So the first one will match exactly this URL:

Re: reliable varnish crash using pcre

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 8/5/15 3:07 AM, Jason Price wrote: if (req.url ~ ^((?!_product).)*$) { Are you certain that this regex really does what you want it to do? It matches a URL with this sequence: * start of string, followed by * zero or more repetitions of *

Re: 503 error from varnish

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 7/5/15 2:54 AM, Tim Dunphy wrote: But my current problem is that I've been able to get the main page to the site cached, and a few others. But when I click to like the 4th or 5th page on the wiki that I want to cache through varnish,

Re: Workspace exhaustion with Varnish 4 under load

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/28/2015 08:25 PM, Geoff Simmons wrote: We're getting our first experience with testing Varnish 4 under load (v4.0.3), and we're having severe problems with workspace exhaustion To follow this up, in case someone finds it in an archive

Workspace exhaustion with Varnish 4 under load

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, We're getting our first experience with testing Varnish 4 under load (v4.0.3), and we're having severe problems with workspace exhaustion - -- LostHeader in the logs, lostheader stats counter increasing, and various VMODs reporting

Re: Workspace exhaustion with Varnish 4 under load

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/28/2015 11:26 PM, Poul-Henning Kamp wrote: I have seen very little info/experience on tuning V4 yet, and have no realistic setup to collect info/experience on myself. Your workspace issue sounds like a clear bug to me, and

Re: Error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/14/2014 04:09 PM, Tobias Karlsson wrote: https://gist.github.com/tokar86a/8e9e8d01c3f206a1630b that is all the information i have in the file. Clearly you believe that, but it isn't possible. Your error message indicates an error in

Header set to NULL by a VMOD: semantic change between 3.0.3 and 3.0.6

Hello all, We're presently testing an upgrade from Varnish 3.0.3 to 3.0.6, and have encountered a change in the semantics of a header evaluated in boolean context after the header has been set to NULL by a VMOD. The attached VTC test passes on 3.0.3 and fails on 3.0.6. The VMOD in question is

Re: Varnish 4.0.1 and IMS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 8/29/14 10:05 PM, Madhusudan Ramanna wrote: I thought Varnish 4.0.1 has support for IMS. But looks like varnish is not sending the IMS header to the backend. Or I'm missing something. *Request 32820 - ReqHeader User-Agent:

Re: varnishlog -m -w

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/28/2014 05:42 PM, Jason Heffner wrote: We are running Varnish 3.0.5-1 from the el6 repo. When trying to use varnishlog with the -w option we are noticing that it ignores the -m option. For instance varnishlog -a -w

Re: Backend-health checks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/06/2014 02:46 PM, Anton Kornexl wrote: in varnishstat after one day: VBE.localhost_1(127.0.0.1,,8080).happy18446743798697425919 . Happy health probes The figure in varnishstat is a 64-bit bitmap, representing the last 64 checks

Re: Cache invalidation with regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/28/2013 06:29 PM, Alexandre wrote: I will wish to invalidate my cache using a regex. example: ^/image.php?a=1b=2* I would like to disable all url starting with ^/image.php?a=1b=2 Do you have an idea for my problem? The '*' in a

Re: Cache invalidation with regex

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/29/2013 11:08 AM, Alexandre wrote: Thank you for your information, but what is the relation with my question ? This is an example. Do you have an idea for the cache invalidation ? Since your regex didn't match your URL example, I thought

Re: Conditional Backend Requests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/03/2012 02:51 PM, Chris Read wrote: Is there any update on when the proposed Backend Conditional Requests feature will make it into Varnish? ( https://www.varnish-cache.org/trac/wiki/BackendConditionalRequests ) The last official word

Re: Varnish client IP address not display

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 3/19/12 9:00 AM, Michael Alger wrote: On Mon, Mar 19, 2012 at 4:36 PM, Jewel Nuruddin wrote: My varnish is run on 10.70.18.22 server and my web server run back end 10.70.18.30 When client browse through varnish in my web server it always

Re: Need some help to speed up varnish

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2/17/12 10:55 AM, Jewel Nuruddin wrote: Here I attached my default.vcl file and /etc/sysconfig/varnish file I check with varnish and without varnish but found without varnish is faster then with varnish. Just a couple of comments about your

Re: how to check whether varnish use memory for cache

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/16/12 04:24 AM, Jewel Nuruddin wrote: I am using malloc for varnish. How can I check malloc is working and also how can I check whether my cached is using this malloc? In Varnish 3.x, varnishstat -1 and varnishadm show you stats about

Re: Does Varnish uses ETag?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 7/7/11 11:14 PM, Kurt Kraut wrote: Does Varnish used ETag to check cache freshness? Mainline Varnish doesn't, but there's an experimental branch 'experimental-ims' on the source repository in which it's implemented. - If yes, how does it

Re: Alert on certain error like 503

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/16/11 01:43 PM, Shibashish wrote: Can varnish be made to send out an alert (mail) in case of an error like 503? I do have a monitoring solution but i can't add all the urls for monitoring. Sometimes varnish gives a 503 and i need to be

Conditional backend requests on repository branch experimental-ims

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello all, The code for the proposed conditional backend request feature (usually If-Modified-Since requests to backends) is now up to date with the current trunk and available on an experimental branch of the source repository called

Re: time out on big object ??

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/30/11 05:39 PM, Patrick CAO HUU THIEN wrote: hello. I made a basic «out of the box» varnish server to access a «personal» web server ... in fact, just define a backend. But I have a problem when I test the download of big object (iso

Re: Your own local Varnish Cache 3.0 release party?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/20/11 07:31 PM, Rubén Romero wrote: As planning of the launch of Varnish 3.0 is on I thought I would ask you all in the list, and at the same sneak the thought in your mind, if it is an idea to hold your own 3 (Varnish 3 heart ;) release

Re: *.keep and if-modified-since

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Following up my own mail, since I forgot something obvious: If you're using the patch, there are a few ways you can verify the IMS feature: In varnishlog you can look for a TxHeader containing If-Modified-Since and/or If-None-Match. Certainly a

Re: *.keep and if-modified-since

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/ 2/11 11:54 PM, Rich Rauenzahn wrote: Do you think we're talking about weeks or months for it to get incorporated into mainline? Not before 3.0 is released. After that, it's hard to say. phk and the team will probably want a solution

Re: Varnish child killed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 4/21/11 10:51 AM, Jean-Francois Laurens wrote: We’re run varnish 2.1.5 for some week now and we still do not understand some behavior regarding the shared memory activity. There's not enough information here for anything better than guesses

Re: web based forum now online

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/14/11 06:18 PM, Per Buer wrote: If you like web forums, I invite you to come on over and hang out. If not, don't. The forum is located at https://www.varnish-cache.org/forum/ Could the forum be set up so that if you already have a

Re: vcl to avoid caching 404

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/ 5/11 05:20 PM, Jonathan Leibiusky wrote: Hi! I am trying to configure varnish to avoid caching some specific http statuses sent from the backend. Since I can't control 100% the headers they are sending, I should do it in varnish as they

Re: Varnish stuck on most served content

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/31/11 11:15 AM, Hettwer, Marian wrote: I'm running Centos 5.5 64bit and here's my varnish startup parameters: DAEMON_OPTS= -a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} \ -f ${VARNISH_VCL_CONF} \ -T 0.0.0.0:6082 \

Re: How to collect lines from varnishncsa only from a specific domain?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/29/11 10:09 PM, Kurt Kraut wrote: I'm trying to use varnishncsa -c -I to collect the output of varnishncsa concerning a specific domain (e.g.: domain.com). I've attempted the following commands: varnishncsa -c -I *domain.com*

Re: Mobile redirect question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/29/11 02:56 PM, Maikel - Songteksten.nl wrote: if ( req.http.user-agent ~

Re: Lots of configs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 3/9/11 12:50 AM, Johnny Halfmoon wrote: Are you proposing some kind of 'hushing' algorithm? Some threads fail silently, whereas other fail verbosely. - -- UPLEX Systemoptimierung Schwanenwik 24 22087 Hamburg http://uplex.de/ Mob: