From varnish-bugs at projects.linpro.no Fri Jun 1 17:42:57 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 01 Jun 2007 17:42:57 -0000 Subject: [Varnish] #110: varnishd leaking virtual memory Message-ID: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> #110: varnishd leaking virtual memory ------------------------+--------------------------------------------------- Reporter: chrisrixon | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Keywords: leak virtual memory ------------------------+--------------------------------------------------- varnish is performing well except it is leaking virtual memory (VIRT in top) I have simple settings: DAEMON_OPTS="-a :80 \ -b localhost:81 \ -s file,/var/lib/varnish/varnish_storage.bin,64M" Virtual mem starts at 256M and then slowly climbs to about 2.5G at which point varnishd is restarted. I am running varnish-1.0.4-2el4.i386.rpm on CentOS 4.4 Thanks Chris. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Jun 2 14:44:13 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 02 Jun 2007 14:44:13 -0000 Subject: [Varnish] #110: varnishd leaking virtual memory In-Reply-To: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> References: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> Message-ID: <065.602afda78090cede905e554b889efced@projects.linpro.no> #110: varnishd leaking virtual memory ---------------------------------+------------------------------------------ Reporter: chrisrixon | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Resolution: Keywords: leak virtual memory | ---------------------------------+------------------------------------------ Comment (by chrisrixon): Here is top info, you can see 3G virtual mem and 95M in mem {{{ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 17538 root 16 0 3037m 95m 70m S 0.3 4.9 0:19.87 varnishd }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 4 22:01:49 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 04 Jun 2007 22:01:49 -0000 Subject: [Varnish] #110: varnishd leaking virtual memory In-Reply-To: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> References: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> Message-ID: <065.1441be3082380c15fc0455f42b778d86@projects.linpro.no> #110: varnishd leaking virtual memory ---------------------------------+------------------------------------------ Reporter: chrisrixon | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Resolution: Keywords: leak virtual memory | ---------------------------------+------------------------------------------ Comment (by cripy): I believe we are having the same issue: http://projects.linpro.no/pipermail/varnish-misc/2007-June/000456.html -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jun 6 07:57:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 06 Jun 2007 07:57:11 -0000 Subject: [Varnish] #111: mgt_vcc.c hard path for /tmp Message-ID: <055.4b93b0530fbb9660baa96e685435e46c@projects.linpro.no> #111: mgt_vcc.c hard path for /tmp -----------------------+---------------------------------------------------- Reporter: nwmcsween | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: -----------------------+---------------------------------------------------- mgt_vcc.c has a hard path for /tmp which is usually mounted noexec / nosuid on hardened servers leading to this: #Problem loading compiled VCL program: /tmp/vcl.XX8cn1K9: failed to map segment from shared object: Operation not permitted {{{ static char * 137 mgt_CallCc(const char *source, struct vsb *sb) 138 { 139 FILE *fo, *fs; 140 char *of, *sf, buf[BUFSIZ]; 141 int i, j, sfd; 142 void *p; 143 144 /* Create temporary C source file */ 145 sf = strdup("/tmp/vcl.XXXXXXXX"); 146 assert(sf != NULL); 147 sfd = mkstemp(sf); 148 if (sfd < 0) { 149 vsb_printf(sb, 150 "Cannot open temporary source file \"%s\": %s\n", 151 sf, strerror(errno)); 152 free(sf); 153 return (NULL); 154 } 155 fs = fdopen(sfd, "r+"); 156 assert(fs != NULL); 157 158 if (fputs(source, fs) < 0 || fflush(fs)) { 159 vsb_printf(sb, 160 "Write error to C source file: %s\n", 161 strerror(errno)); 162 unlink(sf); 163 fclose(fs); 164 return (NULL); 165 } 166 rewind(fs); 167 168 /* Name the output shared library */ 169 of = strdup("/tmp/vcl.XXXXXXXX"); 170 assert(of != NULL); 171 of = mktemp(of); 172 assert(of != NULL); 173 174 /* Attempt to open a pipe to the system C-compiler */ 175 sprintf(buf, 176 "ln -f %s /tmp/_.c ;" /* XXX: for debugging */ 177 "exec cc -fpic -shared -Wl,-x -o %s -x c - < %s 2>&1", 178 sf, of, sf); 179 180 fo = popen(buf, "r"); 181 if (fo == NULL) { 182 vsb_printf(sb, 183 "Internal error: Cannot execute cc(1): %s\n", 184 strerror(errno)); 185 free(of); 186 unlink(sf); 187 fclose(fs); 188 return (NULL); 189 } 190 191 /* If we get any output, it's bad */ 192 j = 0; 193 while (1) { 194 if (fgets(buf, sizeof buf, fo) == NULL) 195 break; 196 if (!j) { 197 vsb_printf(sb, "Internal error: cc(1) complained:\n"); 198 j++; 199 } 200 vsb_cat(sb, buf); 201 } 202 203 i = pclose(fo); 204 if (j == 0 && i != 0) 205 vsb_printf(sb, 206 "Internal error: cc(1) exit status 0x%04x\n", i); 207 208 /* If the compiler complained, or exited non-zero, fail */ 209 if (i || j) { 210 unlink(of); 211 free(of); 212 of = NULL; 213 } 214 215 /* Next, try to load the object into the management process */ 216 p = dlopen(of, RTLD_NOW | RTLD_LOCAL); 217 if (p == NULL) { 218 vsb_printf(sb, "Problem loading compiled VCL program:\n\t%s\n", 219 dlerror()); 220 unlink(of); 221 free(of); 222 of = NULL; 223 } else 224 AZ(dlclose(p)); 225 226 /* clean up and return */ 227 unlink(sf); 228 free(sf); 229 fclose(fs); 230 return (of); 231 } }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 7 12:19:54 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 07 Jun 2007 12:19:54 -0000 Subject: [Varnish] #102: RES_WriteObj() does not send body for POST In-Reply-To: <049.0f1cd63b229c27c45e4086d98e976838@projects.linpro.no> References: <049.0f1cd63b229c27c45e4086d98e976838@projects.linpro.no> Message-ID: <058.3cbf0c4c44e13599ce279aee24a1813f@projects.linpro.no> #102: RES_WriteObj() does not send body for POST ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by knutroy): When using the aforementioned VCL-code to cache POST-requests, Varnish is using GET when fetching from the backend, meaning that the server will see GET while the client is using POST. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 8 14:06:37 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 08 Jun 2007 14:06:37 -0000 Subject: [Varnish] #112: VCL needs an invalidation API Message-ID: <049.2762bb85b91c7448842c959f8ef9ba87@projects.linpro.no> #112: VCL needs an invalidation API -------------------------+-------------------------------------------------- Reporter: des | Owner: des Type: enhancement | Status: new Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: trunk Severity: normal | Keywords: -------------------------+-------------------------------------------------- VCL should have access to an API for controlling the invalidation list (at the very least adding a regexp to the list). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 11 14:27:30 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 11 Jun 2007 14:27:30 -0000 Subject: [Varnish] #113: Problem compiling on mac os x 10.4.9. Message-ID: <048.955404d10560bfc866b2acc8b3e23d03@projects.linpro.no> #113: Problem compiling on mac os x 10.4.9. --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: 1.0.4 Severity: normal | Keywords: --------------------+------------------------------------------------------- Following the mac os x installation instructions here: http://varnish.projects.linpro.no/wiki/Installation I encountered an error while compiling: {{{ /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -include config.h -g -O2 -MT libvarnish_la- vpf.lo -MD -MP -MF .deps/libvarnish_la-vpf.Tpo -c -o libvarnish_la-vpf.lo `test -f 'vpf.c' || echo './'`vpf.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -include config.h -g -O2 -MT libvarnish_la-vpf.lo -MD -MP -MF .deps/libvarnish_la-vpf.Tpo -c vpf.c -fno-common -DPIC -o .libs/libvarnish_la-vpf.o vpf.c:53: error: parse error before ?__dev_t? vpf.c:53: warning: no semicolon at end of struct or union vpf.c:55: error: parse error before ?}? token vpf.c: In function ?vpf_verify?: vpf.c:64: error: dereferencing pointer to incomplete type vpf.c:69: error: dereferencing pointer to incomplete type vpf.c:71: error: dereferencing pointer to incomplete type vpf.c:71: error: dereferencing pointer to incomplete type vpf.c: In function ?vpf_open?: vpf.c:107: error: dereferencing pointer to incomplete type vpf.c:117: error: dereferencing pointer to incomplete type vpf.c:117: error: dereferencing pointer to incomplete type vpf.c:119: error: dereferencing pointer to incomplete type vpf.c:131: error: dereferencing pointer to incomplete type vpf.c:135: error: dereferencing pointer to incomplete type vpf.c:148: error: dereferencing pointer to incomplete type vpf.c:155: error: dereferencing pointer to incomplete type vpf.c:156: error: dereferencing pointer to incomplete type vpf.c:157: error: dereferencing pointer to incomplete type vpf.c: In function ?vpf_write?: vpf.c:179: error: dereferencing pointer to incomplete type vpf.c: In function ?vpf_close?: vpf.c:213: error: dereferencing pointer to incomplete type vpf.c: In function ?_vpf_remove?: vpf.c:234: error: dereferencing pointer to incomplete type vpf.c:236: error: dereferencing pointer to incomplete type vpf.c:240: error: dereferencing pointer to incomplete type vpf.c:247: error: dereferencing pointer to incomplete type make[3]: *** [libvarnish_la-vpf.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 }}} This also happens when trying to build varnish from trunk (rev: 1508). The below patch seems to fix the problem: {{{ Index: lib/libvarnish/vpf.c =================================================================== --- lib/libvarnish/vpf.c (revision 1508) +++ lib/libvarnish/vpf.c (working copy) @@ -50,7 +50,7 @@ struct pidfh { int pf_fd; char pf_path[MAXPATHLEN + 1]; - __dev_t pf_dev; + dev_t pf_dev; ino_t pf_ino; }; }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 11 21:28:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 11 Jun 2007 21:28:18 -0000 Subject: [Varnish] #114: Interger overflow in varnishstat Message-ID: <054.0e913f7269b8683733200996ca0a0065@projects.linpro.no> #114: Interger overflow in varnishstat -------------------------+-------------------------------------------------- Reporter: AndreasR | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishstat | Version: 1.0.4 Severity: minor | Keywords: -------------------------+-------------------------------------------------- I have a question about measuring bandwith usage with varnishstat. I would expect 'Total header bytes' and 'Total header bytes' to be the total number of bytes sent to clients since varnishd was started? Measuring these numbers at different points in time could therefore be used to calculate the bandwith usage. So here are my measurements: * Initial values: 556874988 Total header bytes 20238688347 Total body bytes * 75 minutes later: 848969031 Total header bytes 30800272652 Total body bytes The problem is that the correct values are 40 times larger than what I get from varnishstat. So is this a bug in varnishstat? I notice that the total body bytes is larger than 2^32, perhaps there is an integer overflow somewhere? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jun 12 06:15:41 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Jun 2007 06:15:41 -0000 Subject: [Varnish] #115: Run varnish https mode Message-ID: <057.8fdce5ba8c9cd364077ed1a94b3385bf@projects.linpro.no> #115: Run varnish https mode -------------------------+-------------------------------------------------- Reporter: s.jegadeesh | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: normal | Keywords: -------------------------+-------------------------------------------------- Hello All, How to run varnish in https mode... plz help me.... Thanks, -Jag -- Ticket URL: Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Tue Jun 12 06:21:45 2007 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Tue, 12 Jun 2007 06:21:45 +0000 Subject: [Varnish] #115: Run varnish https mode In-Reply-To: Your message of "Tue, 12 Jun 2007 06:15:41 GMT." <057.8fdce5ba8c9cd364077ed1a94b3385bf@projects.linpro.no> Message-ID: <39637.1181629305@critter.freebsd.dk> In message <057.8fdce5ba8c9cd364077ed1a94b3385bf at projects.linpro.no>, "Varnish" writes: > How to run varnish in https mode... We have not implemented https in Varnish yet. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From varnish-bugs at projects.linpro.no Tue Jun 12 07:08:52 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Jun 2007 07:08:52 -0000 Subject: [Varnish] #115: Run varnish https mode In-Reply-To: <057.8fdce5ba8c9cd364077ed1a94b3385bf@projects.linpro.no> References: <057.8fdce5ba8c9cd364077ed1a94b3385bf@projects.linpro.no> Message-ID: <066.ca0ecbae5276902af63e232f34a8dbfc@projects.linpro.no> #115: Run varnish https mode -------------------------+-------------------------------------------------- Reporter: s.jegadeesh | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: invalid Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => invalid Comment: Support questions should be addressed to the mailing lists. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jun 12 07:10:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Jun 2007 07:10:09 -0000 Subject: [Varnish] #114: Interger overflow in varnishstat In-Reply-To: <054.0e913f7269b8683733200996ca0a0065@projects.linpro.no> References: <054.0e913f7269b8683733200996ca0a0065@projects.linpro.no> Message-ID: <063.af5cc44eafbba15ca1f503a3931b7313@projects.linpro.no> #114: Interger overflow in varnishstat -------------------------+-------------------------------------------------- Reporter: AndreasR | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishstat | Version: 1.0.4 Severity: minor | Resolution: invalid Keywords: | -------------------------+-------------------------------------------------- Changes (by des): * status: new => closed * resolution: => invalid Comment: Nothing wrong with these numbers. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Tue Jun 12 07:13:45 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Tue, 12 Jun 2007 07:13:45 -0000 Subject: [Varnish] #113: Problem compiling on mac os x 10.4.9. In-Reply-To: <048.955404d10560bfc866b2acc8b3e23d03@projects.linpro.no> References: <048.955404d10560bfc866b2acc8b3e23d03@projects.linpro.no> Message-ID: <057.1149f868c9513df6c947aa0892afefbe@projects.linpro.no> #113: Problem compiling on mac os x 10.4.9. --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 1.0.4 Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => closed * resolution: => fixed Comment: Fixed in trunk, thanks. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jun 13 10:41:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 13 Jun 2007 10:41:35 -0000 Subject: [Varnish] #116: Support purging by hostname Message-ID: <051.02818bc70c4abe7424ad7a5676154685@projects.linpro.no> #116: Support purging by hostname -------------------------+-------------------------------------------------- Reporter: gaute | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: purge host hostname -------------------------+-------------------------------------------------- When serving many hosts through varnish it may sometimes be necessary to purge all pages from one host. There would be two ways to support this: 1. make the hostname part of the data a regexp can match against when purging on the admin console. 2. make purging by http/vcl able to take wildcards. The only way to do it now is to somehow get a list of all the cachable urls one host may contain, and purge them all by http. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 14 09:18:24 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 14 Jun 2007 09:18:24 -0000 Subject: [Varnish] #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 Message-ID: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 ----------------------+----------------------------------------------------- Reporter: oh | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Keywords: mac os x ----------------------+----------------------------------------------------- After compiling 1.0.4 on mac os x 10.4.9, running varnishd resulted in the following error: {{{ $ /usr/local/sbin/varnishd -a localhost:8080 -b localhost:80 (null)Assert error in mgt_CallCc(), mgt_vcc.c line 222: Condition((dlclose(p)) == 0) not true. errno = 2 (No such file or directory) }}} In mgt_CallCc() varnish run: {{{ ln -f /tmp/vcl.BvA7YyCF /tmp/_.c ;exec cc -fpic -shared -Wl,-x -o /tmp/vcl.qAK8zcTi -x c - < /tmp/vcl.BvA7YyCF 2>&1 }}} Which results in the following error message: {{{ i686-apple-darwin8-gcc-4.0.1: unrecognized option '-shared' :1: warning: -fpic is not supported; -fPIC assumed /usr/bin/ld: Undefined symbols: _main _VRT_GetHdr _VRT_alloc_backends _VRT_count _VRT_error _VRT_fini_backend _VRT_free_backends _VRT_handling _VRT_l_backend_host _VRT_l_backend_port _VRT_r_obj_cacheable _VRT_r_obj_valid _VRT_r_req_request _VRT_set_backend_name collect2: ld returned 1 exit status }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 14 09:22:01 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 14 Jun 2007 09:22:01 -0000 Subject: [Varnish] #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup Message-ID: <048.530f5b1a0bfe608510abfaf2329f9707@projects.linpro.no> #118: mac os x: Running varnishd results in dyld: lazy symbol binding failed: Symbol not found: _strndup --------------------+------------------------------------------------------- Reporter: oh | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- Running varnishd (trunk) on mac os x results in the following error message: {{{ $ /opt/varnish/sbin/varnishd -a localhost:8080 -b localhost:80 dyld: lazy symbol binding failed: Symbol not found: _strndup Referenced from: /opt/varnish/lib/libvarnish.0.dylib Expected in: flat namespace dyld: Symbol not found: _strndup Referenced from: /opt/varnish/lib/libvarnish.0.dylib Expected in: flat namespace Trace/BPT trap }}} (os x does not have strndup()) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 14 10:00:29 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 14 Jun 2007 10:00:29 -0000 Subject: [Varnish] #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 In-Reply-To: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> References: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> Message-ID: <057.4897f5c04e44c390eb18cf52d74575d9@projects.linpro.no> #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 ----------------------+----------------------------------------------------- Reporter: oh | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: mac os x | ----------------------+----------------------------------------------------- Comment (by oh): Seems like Florians patch http://projects.linpro.no/pipermail/varnish- misc/2007-June/000485.html fixes the problem. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 14 12:59:58 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 14 Jun 2007 12:59:58 -0000 Subject: [Varnish] #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 In-Reply-To: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> References: <048.aa559d5bd4edda6a4d13bc3d880bcb57@projects.linpro.no> Message-ID: <057.afec48c5d4021751cdfabef4e00a2fb9@projects.linpro.no> #117: Mac OS X: Running varnishd results in Assert error in mgt_CallCc(), mgt_vcc.c line 222 ----------------------+----------------------------------------------------- Reporter: oh | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: mac os x | ----------------------+----------------------------------------------------- Comment (by oh): Hmm.. seems like the patch only fixes the problem when varnish is started without a config file. Works: {{{ $ /usr/local/sbin/varnishd -a localhost:8080 -b localhost:80 NB: Limiting size to 2GB on 32 bit architecture to prevent running out of address space. Specifiy explicit size to override. file /tmp/varnish.cWZzCe (unlinked) size 2147479552 bytes (524287 fs- blocks, 524287 pages) Using old SHMFILE }}} Does not work (with the patch I linked to in the previous comment) {{{ $ /usr/local/sbin/varnishd -a localhost:8080 -f /etc/varnish.conf Assert error in mgt_CallCc(), mgt_vcc.c line 214: Condition((dlclose(p)) == 0) not true. errno = 2 (No such file or directory) Abort trap }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 15 10:07:19 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 15 Jun 2007 10:07:19 -0000 Subject: [Varnish] #77: URL rewrite In-Reply-To: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> References: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> Message-ID: <059.1e7904b9cd4825235b2f7f2445ea363b@projects.linpro.no> #77: URL rewrite -------------------------+-------------------------------------------------- Reporter: lapo | Owner: phk Type: enhancement | Status: new Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by gaute): Replying to [ticket:77 lapo]:[[BR]] Just for the record, this is all that varnish would have to do to replace apache (and/or squid) for use with zope & plone, and make a lot of developers like me happy :) {{{ RewriteRule ^/(.*) http://localhost:8080/foo/bar/$1 [P] }}} ( in combination with {{{"if (req.http.host ~ "^www.myhost.com$") {"}}} or with host as a part of the rewrite match expression ) -- Ticket URL: Varnish The Varnish HTTP Accelerator From ssm at linpro.no Fri Jun 15 11:55:11 2007 From: ssm at linpro.no (Stig Sandbeck Mathisen) Date: Fri, 15 Jun 2007 13:55:11 +0200 Subject: [Varnish] #77: URL rewrite In-Reply-To: <059.1e7904b9cd4825235b2f7f2445ea363b@projects.linpro.no> (varnish-bugs@projects.linpro.no's message of "Fri, 15 Jun 2007 10:07:19 -0000") References: <050.43421cdca728d1b8e5023f154c4a71d2@projects.linpro.no> <059.1e7904b9cd4825235b2f7f2445ea363b@projects.linpro.no> Message-ID: <7xlkell9eo.fsf@iostat.e.linpro.no> To elaborate on this, I'd like to be able to use req.http.* variables within the rewrite result: For zope, I could use a rewrite like: {{{ ^/(.*) => "http://localhost:9673/VirtualHostBase/http/" \ . req.http.host \ . ":80/my_plone_sites/fnord.no/$1" }}} Strings between "VirtualHostBase" and "VirtualHostRoot" are used by zope's "Virtual Host Monster" object to generate content and links. In this case, I could use one rewrite rule for many sites. -- Stig Sandbeck Mathisen, Linpro From varnish-bugs at projects.linpro.no Mon Jun 18 08:28:17 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 18 Jun 2007 08:28:17 -0000 Subject: [Varnish] #119: Problem with named servers, if first named server has no user-set name Message-ID: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> #119: Problem with named servers, if first named server has no user-set name ----------------------+----------------------------------------------------- Reporter: cecilihf | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- The introduction of the possibility to name varnish instances introduced a problem that might need som modified behaviour of mgt_param.c. The problem is that if a user starts varnish without specifying a name, this instance gets hostname as name. If the user then starts a new varnish, with another name, the behaviour of mgt_param.c causes this varnish instance to first be named the hostname, same as the first varnish instance, before changing the name to the new name. This is a problem because this results in renaming of the first varnish instance's directory where it stores its temporary filenames. The problem might have to be solved by changing the behaviour of mgt_param.c, so that default values are only set if the user has not specified any other values. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 18 08:28:45 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 18 Jun 2007 08:28:45 -0000 Subject: [Varnish] #119: Problem with named servers, if first named server has no user-set name In-Reply-To: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> References: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> Message-ID: <063.b83b445a799d7dae98cad927f0c6b840@projects.linpro.no> #119: Problem with named servers, if first named server has no user-set name ----------------------+----------------------------------------------------- Reporter: cecilihf | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by cecilihf): * owner: phk => des -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 18 18:13:49 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 18 Jun 2007 18:13:49 -0000 Subject: [Varnish] #110: varnishd leaking virtual memory In-Reply-To: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> References: <056.670fe3911761765f5d209fdf09ceb74b@projects.linpro.no> Message-ID: <065.f088b6686824ae650f17f2b658076fc4@projects.linpro.no> #110: varnishd leaking virtual memory ---------------------------------+------------------------------------------ Reporter: chrisrixon | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: 1.0.4 Severity: major | Resolution: Keywords: leak virtual memory | ---------------------------------+------------------------------------------ Comment (by chrisrixon): This may be helpful: Our site has lots of small requests, PHP database lookups that result in say 100 byte XML files most of which are not cached and have to come from the Apache Backend. So its possible the leak is associated with misses. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Wed Jun 20 13:12:36 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Wed, 20 Jun 2007 13:12:36 -0000 Subject: [Varnish] #47: pass mode does not handle POST In-Reply-To: <049.dce81b215711ded70632456b6f336a2b@projects.linpro.no> References: <049.dce81b215711ded70632456b6f336a2b@projects.linpro.no> Message-ID: <058.89e61dde0505c68978a103f9179fab4b@projects.linpro.no> #47: pass mode does not handle POST ----------------------+----------------------------------------------------- Reporter: des | Owner: des Type: defect | Status: new Priority: high | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by denis at zeno.org): I had no problems with POST until I used Firefox (Safari,Opera and IE all work fine). I also can't see a difference in the header of the browsers, but in the varnishlog I see this when it works: 14 Debug b Pipe Shut read(read)[[BR]] 14 Debug b Pipe Shut write(read) -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 21 06:44:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 21 Jun 2007 06:44:09 -0000 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) In-Reply-To: <052.5d3faee69b391221c7ad7616bcc5599c@projects.linpro.no> References: <052.5d3faee69b391221c7ad7616bcc5599c@projects.linpro.no> Message-ID: <061.1ae3dd55746cc1d0dbc0eb0775ce6619@projects.linpro.no> #105: (varnishd), uid 0: exited on signal 6 (core dumped) ----------------------+----------------------------------------------------- Reporter: patrik | Owner: des Type: defect | Status: assigned Priority: high | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: critical | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * owner: phk => des * status: new => assigned -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 21 06:45:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 21 Jun 2007 06:45:35 -0000 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) In-Reply-To: <052.5d3faee69b391221c7ad7616bcc5599c@projects.linpro.no> References: <052.5d3faee69b391221c7ad7616bcc5599c@projects.linpro.no> Message-ID: <061.1bee2c0c2e54a55f42149b36afed3cc3@projects.linpro.no> #105: (varnishd), uid 0: exited on signal 6 (core dumped) ----------------------+----------------------------------------------------- Reporter: patrik | Owner: des Type: defect | Status: assigned Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * priority: high => normal * version: trunk => 1.0.4 * severity: critical => normal * milestone: Varnish 1.0.4 => Varnish 1.1 -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 06:32:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 06:32:32 -0000 Subject: [Varnish] #120: chdir trick broke -f foo.vcl Message-ID: <049.b90b52a36d33a47423b3109b2a55503b@projects.linpro.no> #120: chdir trick broke -f foo.vcl --------------------+------------------------------------------------------- Reporter: phk | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- After the chdir trick was added, a trivial "./varnishd -d -d -f foo.vcl" fails to find foo.vcl because the pathname is resolved relative to /tmp/$hostname -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 09:15:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 09:15:47 -0000 Subject: [Varnish] #24: VCL compiler memory leaks In-Reply-To: <049.8fbbd5027b28adb4316ce3247c350ba8@projects.linpro.no> References: <049.8fbbd5027b28adb4316ce3247c350ba8@projects.linpro.no> Message-ID: <058.60873d81ba54850bafde206d15a5cb6f@projects.linpro.no> #24: VCL compiler memory leaks ----------------------+----------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: closed Priority: lowest | Milestone: Component: varnishd | Version: trunk Severity: trivial | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: I belive the introduction of TlAlloc() has solved the VCC memory leaks. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 09:31:34 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 09:31:34 -0000 Subject: [Varnish] #37: use SO_RCVTIMEO In-Reply-To: <049.28460f9a7cc12cfdef3a8102861e8209@projects.linpro.no> References: <049.28460f9a7cc12cfdef3a8102861e8209@projects.linpro.no> Message-ID: <058.cfbb5667c37213533e47680a3340114b@projects.linpro.no> #37: use SO_RCVTIMEO -------------------------+-------------------------------------------------- Reporter: phk | Owner: phk Type: enhancement | Status: closed Priority: lowest | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Long since fixed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 09:46:35 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 09:46:35 -0000 Subject: [Varnish] #98: Supervisord and Varnishd In-Reply-To: <055.c8ede2ba5320181fc0b2df5bcdf1ac49@projects.linpro.no> References: <055.c8ede2ba5320181fc0b2df5bcdf1ac49@projects.linpro.no> Message-ID: <064.4904552e5e34737ed577b0ef6996dcd2@projects.linpro.no> #98: Supervisord and Varnishd -------------------------+-------------------------------------------------- Reporter: james at nyi | Owner: phk Type: enhancement | Status: closed Priority: low | Milestone: Varnish 1.1 Component: varnishd | Version: 1.0 Severity: normal | Resolution: fixed Keywords: supervisord | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: I have added a -F option to force varnishd to run in the foreground, hope this helps. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 09:47:47 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 09:47:47 -0000 Subject: [Varnish] #39: workspace confusion In-Reply-To: <049.13b3cac9080ed727ab17101261a3acab@projects.linpro.no> References: <049.13b3cac9080ed727ab17101261a3acab@projects.linpro.no> Message-ID: <058.496ed0d7472fb18ad4e0710a40124e70@projects.linpro.no> #39: workspace confusion ----------------------+----------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: new Priority: low | Milestone: Component: varnishd | Version: Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): Overtaken by events. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 09:47:54 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 09:47:54 -0000 Subject: [Varnish] #39: workspace confusion In-Reply-To: <049.13b3cac9080ed727ab17101261a3acab@projects.linpro.no> References: <049.13b3cac9080ed727ab17101261a3acab@projects.linpro.no> Message-ID: <058.34908c0f986248ee0061abc18d3abb37@projects.linpro.no> #39: workspace confusion ----------------------+----------------------------------------------------- Reporter: phk | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 09:53:32 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 09:53:32 -0000 Subject: [Varnish] #5: Vary header matching In-Reply-To: <049.4feaee8ea6a32c67183c6871dd46c8d6@projects.linpro.no> References: <049.4feaee8ea6a32c67183c6871dd46c8d6@projects.linpro.no> Message-ID: <058.956b999ddc2a268d59472152db862f04@projects.linpro.no> #5: Vary header matching ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Vary is belived to work now, no reports to the contrary received yet. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 10:00:56 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 10:00:56 -0000 Subject: [Varnish] #14: storage_file.c allocation strategy In-Reply-To: <049.09382c923e2c9e00d2c3d94879fad1a0@projects.linpro.no> References: <049.09382c923e2c9e00d2c3d94879fad1a0@projects.linpro.no> Message-ID: <058.1fe38c7223c11cfe704011b30df9786b@projects.linpro.no> #14: storage_file.c allocation strategy ----------------------+----------------------------------------------------- Reporter: des | Owner: phk Type: defect | Status: closed Priority: low | Milestone: Component: varnishd | Version: trunk Severity: minor | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: No current signs of this being a problem. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 10:03:26 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 10:03:26 -0000 Subject: [Varnish] #111: mgt_vcc.c hard path for /tmp In-Reply-To: <055.4b93b0530fbb9660baa96e685435e46c@projects.linpro.no> References: <055.4b93b0530fbb9660baa96e685435e46c@projects.linpro.no> Message-ID: <064.1f359d5408e603285f522608d8d0a278@projects.linpro.no> #111: mgt_vcc.c hard path for /tmp -----------------------+---------------------------------------------------- Reporter: nwmcsween | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | -----------------------+---------------------------------------------------- Changes (by phk): * owner: phk => des Comment: DES has been working on naming varnish instances for multi-varnish compatibility, this ticket belongs in that subproject. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 10:04:45 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 10:04:45 -0000 Subject: [Varnish] #103: Match requested IP to choose backend In-Reply-To: <051.35aca4291907b9902a65618f8a27056d@projects.linpro.no> References: <051.35aca4291907b9902a65618f8a27056d@projects.linpro.no> Message-ID: <060.f6cd9266a2a58389b507e7513adb8b00@projects.linpro.no> #103: Match requested IP to choose backend -------------------------+-------------------------------------------------- Reporter: teddy | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: This should be possible now using the "server.ip" variable. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 10:06:04 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 10:06:04 -0000 Subject: [Varnish] #102: RES_WriteObj() does not send body for POST In-Reply-To: <049.0f1cd63b229c27c45e4086d98e976838@projects.linpro.no> References: <049.0f1cd63b229c27c45e4086d98e976838@projects.linpro.no> Message-ID: <058.b66764052c937018a4a0f4a6a5d5cb79@projects.linpro.no> #102: RES_WriteObj() does not send body for POST ----------------------+----------------------------------------------------- Reporter: des | Owner: DES Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * owner: phk => DES Comment: I think DES already fixed this ? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 10:23:01 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 10:23:01 -0000 Subject: [Varnish] #97: Varnishd fails to start in FreeBSD if IPv6 support is missing in kernel and -T localhost: is used In-Reply-To: <061.520150cb6e2cd14d384b19671cf259ef@projects.linpro.no> References: <061.520150cb6e2cd14d384b19671cf259ef@projects.linpro.no> Message-ID: <070.fca9964ca57c95d37809b9d5f4c2a3e8@projects.linpro.no> #97: Varnishd fails to start in FreeBSD if IPv6 support is missing in kernel and -T localhost: is used -----------------------------+---------------------------------------------- Reporter: anders at fupp.net | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 1.0 Severity: normal | Resolution: fixed Keywords: | -----------------------------+---------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 10:37:48 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 10:37:48 -0000 Subject: [Varnish] #88: Support for http status codes in vcl In-Reply-To: <052.7081411d3e5dcd40e809f6000d3d564c@projects.linpro.no> References: <052.7081411d3e5dcd40e809f6000d3d564c@projects.linpro.no> Message-ID: <061.a9e3b5cd1e9692bebf2a7f378c93d1a1@projects.linpro.no> #88: Support for http status codes in vcl -------------------------+-------------------------------------------------- Reporter: stonor | Owner: phk Type: enhancement | Status: closed Priority: normal | Milestone: Component: varnishd | Version: Severity: normal | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed, there's a resp.status, resp.response and resp.proto variable now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 20:24:34 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 20:24:34 -0000 Subject: [Varnish] #121: Varnishd doesn't work without -d option after naming change Message-ID: <049.e7fee4b62a399d39cba69e6dd05208c4@projects.linpro.no> #121: Varnishd doesn't work without -d option after naming change --------------------+------------------------------------------------------- Reporter: phk | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- After the naming changes varnishd doesn't work without a -d option, likely because the daemon(3) call changes directory. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 21:12:43 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 21:12:43 -0000 Subject: [Varnish] #119: Problem with named servers, if first named server has no user-set name In-Reply-To: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> References: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> Message-ID: <063.256cbe0e08fb59fa2317eb3a44cab336@projects.linpro.no> #119: Problem with named servers, if first named server has no user-set name ----------------------+----------------------------------------------------- Reporter: cecilihf | Owner: des Type: defect | Status: new Priority: normal | Milestone: Varnish 2.0 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by phk): This is fixed now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 21:12:59 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 21:12:59 -0000 Subject: [Varnish] #119: Problem with named servers, if first named server has no user-set name In-Reply-To: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> References: <054.e181f67d458a0988523c636b572f42f4@projects.linpro.no> Message-ID: <063.7e22e328d28c07aa402212b28db5f371@projects.linpro.no> #119: Problem with named servers, if first named server has no user-set name ----------------------+----------------------------------------------------- Reporter: cecilihf | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 2.0 Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 21:13:18 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 21:13:18 -0000 Subject: [Varnish] #121: Varnishd doesn't work without -d option after naming change In-Reply-To: <049.e7fee4b62a399d39cba69e6dd05208c4@projects.linpro.no> References: <049.e7fee4b62a399d39cba69e6dd05208c4@projects.linpro.no> Message-ID: <058.85deb582a0cd451d69bc054f68b6b0c2@projects.linpro.no> #121: Varnishd doesn't work without -d option after naming change --------------------+------------------------------------------------------- Reporter: phk | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: Fixed now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 21:13:29 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 21:13:29 -0000 Subject: [Varnish] #120: chdir trick broke -f foo.vcl In-Reply-To: <049.b90b52a36d33a47423b3109b2a55503b@projects.linpro.no> References: <049.b90b52a36d33a47423b3109b2a55503b@projects.linpro.no> Message-ID: <058.7647eac3304fd6087497179e45c14f6a@projects.linpro.no> #120: chdir trick broke -f foo.vcl --------------------+------------------------------------------------------- Reporter: phk | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: fixed now. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Mon Jun 25 21:14:49 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Mon, 25 Jun 2007 21:14:49 -0000 Subject: [Varnish] #111: mgt_vcc.c hard path for /tmp In-Reply-To: <055.4b93b0530fbb9660baa96e685435e46c@projects.linpro.no> References: <055.4b93b0530fbb9660baa96e685435e46c@projects.linpro.no> Message-ID: <064.dcc486787714df668381ef65e2a0a45e@projects.linpro.no> #111: mgt_vcc.c hard path for /tmp -----------------------+---------------------------------------------------- Reporter: nwmcsween | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: fixed Keywords: | -----------------------+---------------------------------------------------- Changes (by phk): * status: new => closed * resolution: => fixed Comment: With the new -n option sematics, you should be able to give Varnish a working directory not in /tmp: {{{ varnishd -n /home/varnish_work [...] }}} Hope this solves the problem, otherwise yell at me. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 28 18:23:33 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 28 Jun 2007 18:23:33 -0000 Subject: [Varnish] #122: Varnish caches wrong resources Message-ID: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+----------------------------------------------------- The first times I do this: wget http://rudd-o.com/ -S I get this: Resolviendo rudd-o.com... 205.134.246.207 Conectando a rudd-o.com|205.134.246.207|:80... conectado. Petici?n HTTP enviada, esperando respuesta... HTTP/1.1 200 OK Date: Thu, 28 Jun 2007 18:12:53 GMT Server: Apache/2.0.59 (CentOS) X-Powered-By: PHP/5.1.6 X-Pingback: http://rudd-o.com/xmlrpc.php Content-Type: text/html; charset=utf-8 Connection: Close Longitud: no especificado [text/html] That means it's working fine because rudd-o.com/index.php does not generate any caching headers such as ETag or Last-Modified. The problem is, after a while, and completely inexplicably, Varnish starts caching it: rudd-o at gabriela:~/tmp$ wget -S http://rudd-o.com -O /dev/null --13:17:55-- http://rudd-o.com/ => `/dev/null' Resolviendo rudd-o.com... 205.134.246.207 Conectando a rudd-o.com|205.134.246.207|:80... conectado. Petici?n HTTP enviada, esperando respuesta... HTTP/1.1 200 OK Date: Thu, 28 Jun 2007 18:18:10 GMT Server: Apache/2.0.59 (CentOS) X-Powered-By: PHP/5.1.6 X-Pingback: http://rudd-o.com/xmlrpc.php Content-Type: text/html; charset=utf-8 Content-Length: 42796 X-Varnish: 286466621 Via: 1.1 varnish Age: 1 Connection: Keep-Alive Once I did this, nothing I so (such as adding the Pragma: no-cache header) works. Nothing. I can't get that object uncached. That object should not be cached. Help me fix this issue. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 28 18:23:54 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 28 Jun 2007 18:23:54 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.0ebf80839aa201afb8e3b7d4817c2d8f@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by RuddO): GOD DAMN Trac, it ate my line feeds! -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Thu Jun 28 18:24:36 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Thu, 28 Jun 2007 18:24:36 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.540c8d22b0556e8ba2ff1ce4d7e91632@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: new Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by RuddO): Anyway, the point is, Varnish should not cache pages that don't have freshness info set. And it should also obey pragma nocache statements in request headers. -- Ticket URL: Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Thu Jun 28 21:25:40 2007 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu, 28 Jun 2007 21:25:40 +0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: Your message of "Thu, 28 Jun 2007 18:23:33 GMT." <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <1632.1183065940@critter.freebsd.dk> In message <051.90f6a0a9714874d1c39b7d5740eb3b89 at projects.linpro.no>, "Varnish" writes: Check your varnishlog, by default, objects with no specification of cacheability is cached for 120 seconds. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From varnish-bugs at projects.linpro.no Fri Jun 29 07:50:44 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 07:50:44 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.740622939e39bd42d86ec458a977d12b@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: wontfix Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix Comment: Swearing at the developers and / or their tools will get you nowhere. Anyway, this is a configuration issue, not a bug. Use the mailing lists. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 29 07:53:12 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 07:53:12 -0000 Subject: [Varnish] #105: (varnishd), uid 0: exited on signal 6 (core dumped) In-Reply-To: <052.5d3faee69b391221c7ad7616bcc5599c@projects.linpro.no> References: <052.5d3faee69b391221c7ad7616bcc5599c@projects.linpro.no> Message-ID: <061.162cfb8f27b57534e07f05b0f5765494@projects.linpro.no> #105: (varnishd), uid 0: exited on signal 6 (core dumped) ----------------------+----------------------------------------------------- Reporter: patrik | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.1 Component: varnishd | Version: 1.0.4 Severity: normal | Resolution: fixed Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: assigned => closed * resolution: => fixed Comment: Patch committed to trunk. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 29 13:04:11 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 13:04:11 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.e59be6043e1b605eb7b5ec0a694916a1@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Changes (by RuddO): * status: closed => reopened * resolution: wontfix => Comment: 1) I didn't swear at the developers. 2) How is a "random sometimes cache and sometimes not, then don't obey client Pragmas" issue a *configuration* issue? Varnish should only mark objects as cacheable when they are actually *cacheable*, (ETag, perhaps Last-Modified, Expires header sent back), and it surely must NOT deliver objects from cache when the Pragma: no-cache header is sent by the browser. Even if were this a configuration problem, the default configuration should take these elementary facts into account. As it currently stands, you advertise an ACCELERATING CACHE which is broken by default (it accelerates things that shouldn't be accelerated, and disobeys Pragma requirements). Sure, Varnish may have the superior architecture, but your dismissive reply doesn't leave me satisfied one bit. And it certainly doesn't give me any confidence regarding the response I might get on your mailing list. However, in the spirit of showing you my configuration and aiding you in the task of debugging your application so it *improves*, I'm going to paste its relevant part, despite being almost convinced that you don't give a dime: {{{ backend default { set backend.host = "127.0.0.1"; set backend.port = "81"; } backend blogsworks { set backend.host = "127.0.0.1"; set backend.port = "8081"; } sub vcl_recv { if (req.http.host ~ "^(www.)?blogsworks.com") { # let blogsworks web server handle it set req.backend = blogsworks; } else { # these apply to my hosts if ( req.url ~ "wp-content/(uploads|images)" ) { if ( !(req.url ~ "wp-content/(uploads/|)images /gravatar-picture.png$") ) { if ( req.http.referer ~ "^http(|s)://" ) { if ( !(req.http.referer ~ "^http(|s)://(([a-z-]+\.|)rudd-o\.com|([a-z]+\.|)turbochargedcms\.com|faviconsfor\.us|images\.google(.+)|([a-z-]+\.|)hi5\.com|([a-z-]+\.|)planetalinux\.([a-z-]+))" )) { error 403 "Hotlinking is forbidden"; } } } } } # if (req.http.pragma ~ "no-cache" || req.http.cache-control ~ "no- cache") { # # nocaches get the nocache treatment # pipe; # } } }}} The last four commented sentences were commented by me because they had no effect. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 29 13:48:25 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 13:48:25 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.6770736955a57907aa8925e4e33470fd@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by stonor): Varnish defaults to 120 sec. caching if no caching info is given in the HTTP header. This policy is considered a sensible default. You can adjust that with a varnishd option (-t) or in VCL. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 29 16:37:56 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 16:37:56 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.a898a365c051caf875e80a9e5312151b@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: reopened Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+----------------------------------------------------- Comment (by RuddO): Instead of defaulting to 120s if no headers are present, it must by default not cache stale objects or objects without caching headers, and cache objects with only Last-Modified headers using an adaptive TTL. Static files served by Apache always have last-modified headers, so it's sensible to use this approach (plus, you have the ETag thingie that Apache returns). Dynamic PHP/CGI/Python scripts (configured not to send any uncaching headers) on the other hand must never be cached because the freshness of the page is *uncertain*. Those scripts that actually send headers saying "hey, cache me, man", they must be cached. That is, an object should be marked cacheable by adaptive TTL *only* if it has a Last-Modified header (see the cacheability engine for more info), or if it has an Expires header (in which case it shouldn't use an adaptive TTL, it should rather use the explicit Expires time). And the -t option should enable the current default behavior of assigning N second TTL. And this particular behavior should be documented in big red typeface on the front page or the varnish docs. So, if I use -t 0, then nothing gets cached unless an Expires header is present? Doesn't really make sense, since the sensible default would be an adaptive TTL based on Last-Modified to cache static files transparently (you know, Apache doesn't serve them with Expires: headers). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 29 17:35:25 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 17:35:25 -0000 Subject: [Varnish] #123: initscript bug Message-ID: <051.52dec2edc933e46f7696c0c9c94ba156@projects.linpro.no> #123: initscript bug --------------------+------------------------------------------------------- Reporter: RuddO | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Keywords: --------------------+------------------------------------------------------- daemon --pidfile ${PIDFILE} ${DAEMON} "$DAEMON_OPTS" -P ${PIDFILE} #> /dev/null 2>&1 the --pidfile is causing varnish not to start I had to comment the dev null arguments at the end to find out about that root at serv2 [/etc/httpd/conf]# rpm -q centos-release centos-release-4-4.3 There ya go. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Fri Jun 29 17:39:04 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Fri, 29 Jun 2007 17:39:04 -0000 Subject: [Varnish] #123: initscript bug In-Reply-To: <051.52dec2edc933e46f7696c0c9c94ba156@projects.linpro.no> References: <051.52dec2edc933e46f7696c0c9c94ba156@projects.linpro.no> Message-ID: <060.a760f367bea34604ed94db6a67db5dcb@projects.linpro.no> #123: initscript bug --------------------+------------------------------------------------------- Reporter: RuddO | Owner: des Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by RuddO): killproc -p $PIDFILE $DAEMON also fails -- Ticket URL: Varnish The Varnish HTTP Accelerator From phk at phk.freebsd.dk Fri Jun 29 22:39:05 2007 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Fri, 29 Jun 2007 22:39:05 +0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: Your message of "Fri, 29 Jun 2007 16:37:56 GMT." <060.a898a365c051caf875e80a9e5312151b@projects.linpro.no> Message-ID: <7036.1183156745@critter.freebsd.dk> In message <060.a898a365c051caf875e80a9e5312151b at projects.linpro.no>, "Varnish" writes: >Comment (by RuddO): > > Instead of defaulting to 120s if no headers are present, it must by > default not cache stale objects or objects without caching headers, and > cache objects with only Last-Modified headers using an adaptive TTL. I'm sorry, but you are obviously confusing Varnish with a client side cache. Please read the rationale for our decision, which is well documented already. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From varnish-bugs at projects.linpro.no Sat Jun 30 08:10:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 30 Jun 2007 08:10:09 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.aaeab462d38a11d8668da14689a94554@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: wontfix Keywords: | ----------------------+----------------------------------------------------- Changes (by des): * status: reopened => closed * resolution: => wontfix Comment: This discussion belongs on the mailing lists, not in the ticket system. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Jun 30 08:11:28 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 30 Jun 2007 08:11:28 -0000 Subject: [Varnish] #123: initscript bug In-Reply-To: <051.52dec2edc933e46f7696c0c9c94ba156@projects.linpro.no> References: <051.52dec2edc933e46f7696c0c9c94ba156@projects.linpro.no> Message-ID: <060.fa788be85d816919d7c4f7e6b29c7580@projects.linpro.no> #123: initscript bug --------------------+------------------------------------------------------- Reporter: RuddO | Owner: des Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: wontfix Keywords: | --------------------+------------------------------------------------------- Changes (by des): * status: new => closed * resolution: => wontfix Comment: Content-free ticket. Please seek assistance on the mailing lists before deciding that the behaviour you are seeing is a bug. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at projects.linpro.no Sat Jun 30 13:14:09 2007 From: varnish-bugs at projects.linpro.no (Varnish) Date: Sat, 30 Jun 2007 13:14:09 -0000 Subject: [Varnish] #122: Varnish caches wrong resources In-Reply-To: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> References: <051.90f6a0a9714874d1c39b7d5740eb3b89@projects.linpro.no> Message-ID: <060.c2e1fc8077ed9c36d843c129d0d38289@projects.linpro.no> #122: Varnish caches wrong resources ----------------------+----------------------------------------------------- Reporter: RuddO | Owner: phk Type: defect | Status: closed Priority: normal | Milestone: Varnish 1.0.4 Component: varnishd | Version: trunk Severity: normal | Resolution: wontfix Keywords: | ----------------------+----------------------------------------------------- Comment (by RuddO): Gee, thanks. I already sent a couple of mails to varnish-dev and no reply yet. I always thought bug reports belonged in a bug tracker. Guess I've been wrong all my life. -- Ticket URL: Varnish The Varnish HTTP Accelerator