From varnish-bugs at varnish-cache.org Tue Mar 1 21:51:22 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 01 Mar 2016 21:51:22 -0000 Subject: [Varnish] #1864: Assert error in BAN_CheckObject() In-Reply-To: <043.16ef0498d962136d0f77108fdaee3dd2@varnish-cache.org> References: <043.16ef0498d962136d0f77108fdaee3dd2@varnish-cache.org> Message-ID: <058.bd22107a45450f05928022952c2607c5@varnish-cache.org> #1864: Assert error in BAN_CheckObject() ----------------------+---------------------------------------- Reporter: batty | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.1.1 Severity: major | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Changes (by Poul-Henning Kamp ): * owner: => Poul-Henning Kamp * status: new => closed * resolution: => fixed Comment: In [c1bc0d8ecee281d585d23173921ee8676421462f]: {{{ #!CommitTicketReference repository="" revision="c1bc0d8ecee281d585d23173921ee8676421462f" Snapshot & refcount the final ban to check, to avoid running of the ban-list if the lurker washes this OC while we check it. Mostly diagnosed by: Martin Fixes: #1864 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 2 16:55:44 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 02 Mar 2016 16:55:44 -0000 Subject: [Varnish] #1840: add beresp.backend.name field to vcl_error In-Reply-To: <045.b0945da6e5dc0a4631d714d8311cefa1@varnish-cache.org> References: <045.b0945da6e5dc0a4631d714d8311cefa1@varnish-cache.org> Message-ID: <060.85e08316e8a73b64e84eb7ef68fb06da@varnish-cache.org> #1840: add beresp.backend.name field to vcl_error -------------------------+---------------------- Reporter: jzinner | Owner: Type: enhancement | Status: closed Priority: normal | Milestone: Component: build | Version: unknown Severity: normal | Resolution: wontfix Keywords: | -------------------------+---------------------- Changes (by fgsch): * status: new => closed * resolution: => wontfix Comment: This works in recent versions of 4.0, 4.1 and master. If you're still in 3.0 please upgrade to a more recent version. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 2 16:57:44 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 02 Mar 2016 16:57:44 -0000 Subject: [Varnish] #1865: Panic accessing beresp.backend.ip in vcl_backend_error{} Message-ID: <043.c76c6a2ec196f707970ecd26dd286f60@varnish-cache.org> #1865: Panic accessing beresp.backend.ip in vcl_backend_error{} ----------------------+------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Keywords: ----------------------+------------------- {{{ *** v1 4.9 debug| Error: Child (29918) died signal=6 (core dumped)\n *** v1 4.9 debug| Error: Child (29918) Panic at: Wed, 02 Mar 2016 16:51:44 GMT\n *** v1 4.9 debug| "Assert error in vbe_dir_getip(), cache/cache_backend.c line 262:\n *** v1 4.9 debug| Condition((bo->htc) != NULL) not true.\n *** v1 4.9 debug| errno = 110 (Connection timed out)\n *** v1 4.9 debug| thread = (cache-worker)\n *** v1 4.9 debug| version = varnish-trunk revision 67f2e57\n *** v1 4.9 debug| ident = Linux,4.3.0-1-amd64,x86_64,-jnone,-smalloc,-smalloc,-hcritbit,epoll\n *** v1 4.9 debug| Backtrace:\n *** v1 4.9 debug| 0x43bd41: pan_backtrace+0x1d\n *** v1 4.9 debug| 0x43c149: pan_ic+0x2bc\n *** v1 4.9 debug| 0x41213a: vbe_dir_getip+0x155\n *** v1 4.9 debug| 0x41d21e: VDI_GetIP+0x18a\n *** v1 4.9 debug| 0x453cff: VRT_r_beresp_backend_ip+0xe9\n *** v1 4.9 debug| 0x7ffb239fbaf4: vgc.so(VGC_function_vcl_backend_error+0x34) [0x7ffb239fbaf4]\n *** v1 4.9 debug| 0x44bf8d: vcl_call_method+0x527\n *** v1 4.9 debug| 0x44c18c: VCL_backend_error_method+0x164\n *** v1 4.9 debug| 0x428a64: vbf_stp_error+0x3c2\n *** v1 4.9 debug| 0x42932e: vbf_fetch_thread+0x3d0\n ... }}} Testcase attached. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 2 18:56:15 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 02 Mar 2016 18:56:15 -0000 Subject: [Varnish] #1662: BereqProtocol showing twice for HTTP 1.0 requests In-Reply-To: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> References: <043.cd65aaf168b645e5087eb24ca7cc84b1@varnish-cache.org> Message-ID: <058.d6e01a39e23a410f09950d0fa27ddcdb@varnish-cache.org> #1662: BereqProtocol showing twice for HTTP 1.0 requests --------------------+--------------------- Reporter: fgsch | Owner: aondio Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: trunk Severity: normal | Resolution: fixed Keywords: | --------------------+--------------------- Changes (by Federico G. Schwindt ): * status: new => closed * resolution: => fixed Comment: In [51e92b447c64f88afa3feb368f41a1136711aaa8]: {{{ #!CommitTicketReference repository="" revision="51e92b447c64f88afa3feb368f41a1136711aaa8" Log calls http_ForceField() in VSL using xxxUnset Previously we would force the protocol and method fields to HTTP/1.1 and GET, respectively, but hide this from VSL showing 2 different entries for BereqProtocol and/or BereqMethod. Discussed with arianna at . Fixes #1662 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 2 19:04:05 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 02 Mar 2016 19:04:05 -0000 Subject: [Varnish] #1865: Panic accessing beresp.backend.ip in vcl_backend_error{} In-Reply-To: <043.c76c6a2ec196f707970ecd26dd286f60@varnish-cache.org> References: <043.c76c6a2ec196f707970ecd26dd286f60@varnish-cache.org> Message-ID: <058.1a5cabf63d98508c32784f169a54e5b4@varnish-cache.org> #1865: Panic accessing beresp.backend.ip in vcl_backend_error{} ----------------------+-------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Description changed by fgsch: Old description: > {{{ > *** v1 4.9 debug| Error: Child (29918) died signal=6 (core dumped)\n > *** v1 4.9 debug| Error: Child (29918) Panic at: Wed, 02 Mar 2016 > 16:51:44 GMT\n > *** v1 4.9 debug| "Assert error in vbe_dir_getip(), > cache/cache_backend.c line 262:\n > *** v1 4.9 debug| Condition((bo->htc) != NULL) not true.\n > *** v1 4.9 debug| errno = 110 (Connection timed out)\n > *** v1 4.9 debug| thread = (cache-worker)\n > *** v1 4.9 debug| version = varnish-trunk revision 67f2e57\n > *** v1 4.9 debug| ident = > Linux,4.3.0-1-amd64,x86_64,-jnone,-smalloc,-smalloc,-hcritbit,epoll\n > *** v1 4.9 debug| Backtrace:\n > *** v1 4.9 debug| 0x43bd41: pan_backtrace+0x1d\n > *** v1 4.9 debug| 0x43c149: pan_ic+0x2bc\n > *** v1 4.9 debug| 0x41213a: vbe_dir_getip+0x155\n > *** v1 4.9 debug| 0x41d21e: VDI_GetIP+0x18a\n > *** v1 4.9 debug| 0x453cff: VRT_r_beresp_backend_ip+0xe9\n > *** v1 4.9 debug| 0x7ffb239fbaf4: > vgc.so(VGC_function_vcl_backend_error+0x34) [0x7ffb239fbaf4]\n > *** v1 4.9 debug| 0x44bf8d: vcl_call_method+0x527\n > *** v1 4.9 debug| 0x44c18c: VCL_backend_error_method+0x164\n > *** v1 4.9 debug| 0x428a64: vbf_stp_error+0x3c2\n > *** v1 4.9 debug| 0x42932e: vbf_fetch_thread+0x3d0\n > ... > }}} > > Testcase attached. New description: {{{ *** v1 4.9 debug| Error: Child (28106) died signal=6 (core dumped)\n *** v1 4.9 debug| Error: Child (28106) Panic at: Wed, 02 Mar 2016 19:03:50 GMT\n *** v1 4.9 debug| "Assert error in VDI_GetIP(), cache/cache_director.c line 122:\n *** v1 4.9 debug| Condition(bo->director_state == DIR_S_HDRS || bo->director_state == DIR_S_BODY) not true.\n *** v1 4.9 debug| errno = 110 (Connection timed out)\n *** v1 4.9 debug| thread = (cache-worker)\n *** v1 4.9 debug| version = varnish-trunk revision 51e92b4\n *** v1 4.9 debug| ident = Linux,4.3.0-1-amd64,x86_64,-jnone,-smalloc,-smalloc,-hcritbit,epoll\n *** v1 4.9 debug| Backtrace:\n *** v1 4.9 debug| 0x43bdc7: pan_backtrace+0x1d\n *** v1 4.9 debug| 0x43c1cf: pan_ic+0x2bc\n *** v1 4.9 debug| 0x41d202: VDI_GetIP+0x16e\n *** v1 4.9 debug| 0x453d85: VRT_r_beresp_backend_ip+0xe9\n *** v1 4.9 debug| 0x7fbb955fba0d: vgc.so(VGC_function_vcl_backend_error+0x2d) [0x7fbb955fba0d]\n *** v1 4.9 debug| 0x44c013: vcl_call_method+0x527\n *** v1 4.9 debug| 0x44c212: VCL_backend_error_method+0x164\n *** v1 4.9 debug| 0x428aa5: vbf_stp_error+0x3c2\n *** v1 4.9 debug| 0x42936f: vbf_fetch_thread+0x3d0\n *** v1 4.9 debug| 0x458b2e: Pool_Work_Thread+0x512\n ... }}} Testcase attached. -- -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 2 19:05:53 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Wed, 02 Mar 2016 19:05:53 -0000 Subject: [Varnish] #1865: Panic accessing beresp.backend.ip in vcl_backend_error{} In-Reply-To: <043.c76c6a2ec196f707970ecd26dd286f60@varnish-cache.org> References: <043.c76c6a2ec196f707970ecd26dd286f60@varnish-cache.org> Message-ID: <058.a849e52d31c68ee1f2dfb8911118700d@varnish-cache.org> #1865: Panic accessing beresp.backend.ip in vcl_backend_error{} ----------------------+-------------------- Reporter: fgsch | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishd | Version: trunk Severity: normal | Resolution: Keywords: | ----------------------+-------------------- Comment (by fgsch): OTOH beresp.backend.name is perfectly available. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 3 09:49:45 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 03 Mar 2016 09:49:45 -0000 Subject: [Varnish] #1863: Assert error in child_sigsegv_handler() In-Reply-To: <043.25edbd1166f396845e72d7946fde9079@varnish-cache.org> References: <043.25edbd1166f396845e72d7946fde9079@varnish-cache.org> Message-ID: <058.ea1015f9d4e8853403525057c00d7941@varnish-cache.org> #1863: Assert error in child_sigsegv_handler() ----------------------+----------------------------------------------- Reporter: batty | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.1.1 Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Changes (by Martin Blix Grydeland ): * status: new => closed * owner: => Martin Blix Grydeland * resolution: => fixed Comment: In [9b31cf338e93418571bfa6114fbb197143811493]: {{{ #!CommitTicketReference repository="" revision="9b31cf338e93418571bfa6114fbb197143811493" Don't reset the oc->ban pointer from BAN_CheckObject Resetting the pointer would race against the ban lurker moving the OC in the ban list and any object event listeners wanting to see the new ban timestamp on OEV_BANCHG. Fixes: #1863 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 3 09:52:55 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 03 Mar 2016 09:52:55 -0000 Subject: [Varnish] #1864: Assert error in BAN_CheckObject() In-Reply-To: <043.16ef0498d962136d0f77108fdaee3dd2@varnish-cache.org> References: <043.16ef0498d962136d0f77108fdaee3dd2@varnish-cache.org> Message-ID: <058.1c63b03300d331beccd562e5cf903e5d@varnish-cache.org> #1864: Assert error in BAN_CheckObject() ----------------------+---------------------------------------- Reporter: batty | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.1.1 Severity: major | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Comment (by Martin Blix Grydeland ): In [ea9e3aa324e9e491540ddcf846038778f4696613]: {{{ #!CommitTicketReference repository="" revision="ea9e3aa324e9e491540ddcf846038778f4696613" Snapshot & refcount the final ban to check, to avoid running of the ban-list if the lurker washes this OC while we check it. Mostly diagnosed by: Martin Fixes: #1864 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 3 09:52:55 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 03 Mar 2016 09:52:55 -0000 Subject: [Varnish] #1863: Assert error in child_sigsegv_handler() In-Reply-To: <043.25edbd1166f396845e72d7946fde9079@varnish-cache.org> References: <043.25edbd1166f396845e72d7946fde9079@varnish-cache.org> Message-ID: <058.a8aaccbbd3de5a95ae3669157a368e66@varnish-cache.org> #1863: Assert error in child_sigsegv_handler() ----------------------+----------------------------------------------- Reporter: batty | Owner: Martin Blix Grydeland Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.1.1 Severity: major | Resolution: fixed Keywords: | ----------------------+----------------------------------------------- Comment (by Martin Blix Grydeland ): In [ea2d74c4ac20a2182ad8e717076ad912fe2b5994]: {{{ #!CommitTicketReference repository="" revision="ea2d74c4ac20a2182ad8e717076ad912fe2b5994" Don't reset the oc->ban pointer from BAN_CheckObject Resetting the pointer would race against the ban lurker moving the OC in the ban list and any object event listeners wanting to see the new ban timestamp on OEV_BANCHG. Fixes: #1863 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 3 16:28:31 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 03 Mar 2016 16:28:31 -0000 Subject: [Varnish] #1864: Assert error in BAN_CheckObject() In-Reply-To: <043.16ef0498d962136d0f77108fdaee3dd2@varnish-cache.org> References: <043.16ef0498d962136d0f77108fdaee3dd2@varnish-cache.org> Message-ID: <058.85903a3b94578a34fd24f864c8b96571@varnish-cache.org> #1864: Assert error in BAN_CheckObject() ----------------------+---------------------------------------- Reporter: batty | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: varnishd | Version: 4.1.1 Severity: major | Resolution: fixed Keywords: | ----------------------+---------------------------------------- Comment (by batty): Thanks for the quick turnaround on this! Any idea on when the change may be available in a release? -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Thu Mar 3 16:50:05 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Thu, 03 Mar 2016 16:50:05 -0000 Subject: [Varnish] #1859: Average Hitrate Reported by Varnishstat Inaccurate In-Reply-To: <043.84daa5379ecc7197454a1af0d51ed7ec@varnish-cache.org> References: <043.84daa5379ecc7197454a1af0d51ed7ec@varnish-cache.org> Message-ID: <058.238c015f1f46cef600c9055a2ce60819@varnish-cache.org> #1859: Average Hitrate Reported by Varnishstat Inaccurate ---------------------------------+-------------------- Reporter: batty | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: varnishstat | Version: 4.1.1 Severity: normal | Resolution: Keywords: varnishtat hit rate | ---------------------------------+-------------------- Comment (by batty): This does not appear to be an issue in version 4.0.3. We downgraded one server in our tier to version 4.0.3 so that it is running beside 4.1.1. The servers are load balanced using a least connection algorithm. I ran varnishstat on each and let it run for 5 minutes. Here are the results reported for hitrate n: 4.0.3 {{{ Hitrate n: 10 100 299 avg(n): 0.6947 0.6813 0.6921 }}} 4.1.1 {{{ Hitrate n: 10 100 305 avg(n): 0.1956 0.1585 0.1578 }}} Here are the hit/miss metrics since varnish was last restarted for each: 4.0.3 {{{ MAIN.cache_hit 2788195 16.45 Cache hits MAIN.cache_miss 1357351 8.01 Cache misses 2788195 / (2788195 + 1357351) = .6726 }}} 4.1.1 {{{ MAIN.cache_hit 3776402 17.96 Cache hits MAIN.cache_miss 1736464 8.26 Cache misses 3776402 / (3776402 + 1736464) = .6850 }}} The ~69% hit rate reported by varnishstat in version 4.0.3 is accurate. The rate reported by version 4.1.1 seems way off. Note: The total hit/miss metric counts are not similar between the two servers because the server running varnish 4.1.1 has been running longer. -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 4 13:20:39 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 04 Mar 2016 13:20:39 -0000 Subject: [Varnish] #1855: varnishstat width is limited to 999GB (12 chars) for byte counters In-Reply-To: <043.645c04c96f766732bf122865b24e378a@varnish-cache.org> References: <043.645c04c96f766732bf122865b24e378a@varnish-cache.org> Message-ID: <058.e82d9ce601a16beff53e3834f2f220bc@varnish-cache.org> #1855: varnishstat width is limited to 999GB (12 chars) for byte counters -------------------------+--------------------------------------------- Reporter: fgsch | Owner: Federico G. Schwindt Type: defect | Status: closed Priority: normal | Milestone: Component: varnishstat | Version: trunk Severity: normal | Resolution: fixed Keywords: | -------------------------+--------------------------------------------- Changes (by Federico G. Schwindt ): * owner: => Federico G. Schwindt * status: new => closed * resolution: => fixed Comment: In [81d5d4626690fdff586a7a40a89279d3deb9bb60]: {{{ #!CommitTicketReference repository="" revision="81d5d4626690fdff586a7a40a89279d3deb9bb60" Truncate output if it's wider than 12 chars Early version of the patch OK'd by martin at . Fixes #1855. }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Fri Mar 4 14:53:49 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Fri, 04 Mar 2016 14:53:49 -0000 Subject: [Varnish] #1860: ESI-related memory leaks In-Reply-To: <043.d1642b45ea53a8b5b5d2ad09c0caf12c@varnish-cache.org> References: <043.d1642b45ea53a8b5b5d2ad09c0caf12c@varnish-cache.org> Message-ID: <058.940d1430b179395c9bb983df43ea65cc@varnish-cache.org> #1860: ESI-related memory leaks --------------------+---------------------------------------- Reporter: daghf | Owner: Poul-Henning Kamp Type: defect | Status: closed Priority: normal | Milestone: Component: build | Version: 4.1.2 Severity: normal | Resolution: fixed Keywords: | --------------------+---------------------------------------- Comment (by Lasse Karstensen ): In [36f80ab5c2cb743c78d67c6e0771c3ff972568e2]: {{{ #!CommitTicketReference repository="" revision="36f80ab5c2cb743c78d67c6e0771c3ff972568e2" Always close the VFP stack, also on BS_NONE. Fixes: #1860 }}} -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Tue Mar 8 08:21:09 2016 From: varnish-bugs at varnish-cache.org (Varnish) Date: Tue, 08 Mar 2016 08:21:09 -0000 Subject: [Varnish] #1866: varnishncsa stops consuming logs after Assert error in vslc_vsm_next() Message-ID: <044.2992c85b9ed2f3f96948f242ff9436b5@varnish-cache.org> #1866: varnishncsa stops consuming logs after Assert error in vslc_vsm_next() --------------------+------------------------- Reporter: johtru | Type: defect Status: new | Priority: normal Milestone: | Component: varnishncsa Version: 4.1.1 | Severity: normal Keywords: | --------------------+------------------------- Last night, our logging pipe showed no web traffic data since our varnishncsa process had suddenly stopped to consume the varnishd shared memory log. The only output documenting the failure we got was captured on stderr and read: {{{ Mar 07 11:03:59 web-front-01 varnishncsa-syslog-wrapper[889]: Assert error in vslc_vsm_next(), vsl_cursor.c line 130: Mar 07 11:03:59 web-front-01 varnishncsa-syslog-wrapper[889]: Condition((t) != 0) not true. }}} Cursiously, that did not cause the process to terminate - it just stopped relaying log data. We're using varnichncsa to relay access logs to other hosts via syslog for analysis. For that purpose, we have a systemd service that wraps the varnishncsa binary like so: {{{ #!/bin/bash export LC_ALL=C FORMAT='%{VCL_Log:vxid}x %{X-BE}o %{Host}i %h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-agent}i\" TIME=%D %{Varnish:time_firstbyte}x %{Varnish:handling}x XFP=%{X-Forwarded-Proto}i CT=%{Content-Type}o XFF=%{X -Forwarded-For}i' TAG="varnishncsa" PRIORITY="local0.info" /usr/bin/varnishncsa -g request -F "${FORMAT}" | /usr/local/bin/logger.pl -t "${TAG}" -p "${PRIORITY}" }}} (The pipe's consumer, `logger.pl`, is a tiny Perl script that works around a peculiarity of systemd, which would make all logs show up in the system's journal, as well as relaying elsewhere via syslog.) The box we have this running on receives ~1500reqs/s, and is equipped with ECC RDIMM. The hardware was tested for reliability extensively before having been put into service, so I think we can safely rule out memory problems. We're running Debian Jessie with the latest backports Kernel (4.3+70~bpo8+1, 4.3.0-0.bpo.1-amd64). -- Ticket URL: Varnish The Varnish HTTP Accelerator From varnish-bugs at varnish-cache.org Wed Mar 16 12:00:15 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Wed, 16 Mar 2016 17:30:15 +0530 Subject: Document1 Message-ID: <98E9AFDB018E75545F769C1D1873765E41E20EE2@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document1.zip Type: application/zip Size: 3101 bytes Desc: Document1.zip URL: From varnish-bugs at varnish-cache.org Wed Mar 16 15:34:25 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Wed, 16 Mar 2016 21:04:25 +0530 Subject: Document2 Message-ID: <0A71ED3484390E500D7708E9@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 3017 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 17 10:05:01 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 17 Mar 2016 14:05:01 +0400 Subject: Document26 Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document26.zip Type: application/zip Size: 3515 bytes Desc: Document26.zip URL: From varnish-bugs at varnish-cache.org Fri Mar 18 12:09:05 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Fri, 18 Mar 2016 08:09:05 -0400 Subject: Document2 Message-ID: <55B983BA68A3AC0BAA1415B86C88BC220BF1A99B@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 5245 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Fri Mar 18 17:18:35 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Fri, 18 Mar 2016 20:18:35 +0300 Subject: Document2 Message-ID: <19C4FB1CC839404A1E7C876209AB9059856ED@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 4329 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Tue Mar 22 12:29:36 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 22 Mar 2016 17:59:36 +0530 Subject: Document 2 Message-ID: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document 2.zip Type: application/zip Size: 3202 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Wed Mar 23 10:49:27 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs) Date: Wed, 23 Mar 2016 13:49:27 +0300 Subject: Image836512703785.pdf Message-ID: Sent from my Sony Xperia? smartphone -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Image836512703785.zip Type: application/x-zip Size: 3388 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Wed Mar 23 12:11:49 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs) Date: Wed, 23 Mar 2016 15:11:49 +0300 Subject: Image5894628951860.pdf Message-ID: <77A2CC-64EF6E862FD9E991352FCD5084064C5@varnish-cache.org> Sent from my Sony Xperia? smartphone -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Image5894628951860.zip Type: application/octet-stream Size: 3445 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Wed Mar 23 13:14:59 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs) Date: Wed, 23 Mar 2016 13:14:59 -0000 Subject: Image81577710347168.pdf Message-ID: <3916F7-BA2C3215B45CD7D2B30EEEDD17D4EBB@varnish-cache.org> Sent from my Sony Xperia? smartphone -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Image81577710347168.zip Type: application/x-zip-compressed Size: 3491 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Wed Mar 23 13:34:21 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs) Date: Wed, 23 Mar 2016 20:34:21 +0700 Subject: Image191994077761.pdf Message-ID: Sent from my Sony Xperia? smartphone -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Image191994077761.zip Type: application/x-zip-compressed Size: 3387 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Wed Mar 23 13:36:39 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs) Date: Wed, 23 Mar 2016 08:36:39 -0500 Subject: Image813693540688.pdf Message-ID: Sent from my Sony Xperia? smartphone -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Image813693540688.zip Type: application/octet-stream Size: 3482 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Wed Mar 23 23:15:52 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs) Date: Wed, 23 Mar 2016 17:15:52 -0600 Subject: Image071825228761.pdf Message-ID: <5F4911-25D80848E679FB90051B30157D7D0EB@varnish-cache.org> Sent from my Sony Xperia? smartphone -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Image071825228761.zip Type: application/octet-stream Size: 3545 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Thu Mar 24 13:19:45 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 16:19:45 +0300 Subject: Document2 Message-ID: <51844D612ED4F37CECDB44C0F09E90BD3C@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 3869 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 24 12:32:22 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 15:32:22 +0300 Subject: Document2 Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 5319 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 24 12:50:54 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 14:50:54 +0200 Subject: Document2 Message-ID: <6552440A2F16E82C3761379570CB1107C626F5D@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 3898 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 24 14:05:37 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 19:35:37 +0530 Subject: Document2 Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 5287 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 24 13:27:20 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 15:27:20 +0200 Subject: Document2 Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 5356 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 24 14:58:36 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 07:58:36 -0700 Subject: Document2 Message-ID: <18FA01B7EBAD555977D675E848F088@BORO-SBS.boro.local> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 3883 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Thu Mar 24 15:54:29 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Thu, 24 Mar 2016 08:54:29 -0700 Subject: Document2 Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Document2.zip Type: application/zip Size: 3878 bytes Desc: Document2.zip URL: From varnish-bugs at varnish-cache.org Fri Mar 25 12:47:56 2016 From: varnish-bugs at varnish-cache.org (Laverne Valencia) Date: Fri, 25 Mar 2016 15:47:56 +0300 Subject: FW: Invoice Copy Message-ID: <655401099078495.0722CFF68B@varnish-cache.org> Dear varnish-bugs, Please review the attached copy of your Invoice (number: IN024484) for an amount of $8127.63. Thank you for your business. Laverne Valencia Sales Director -------------- next part -------------- A non-text attachment was scrubbed... Name: varnish-bugs-invoicecopy_024484.zip Type: application/zip Size: 16094 bytes Desc: not available URL: From varnish-bugs at varnish-cache.org Tue Mar 29 12:49:36 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 29 Mar 2016 18:19:36 +0530 Subject: CCE29032016_00059.jpg Message-ID: <26900E0F-3A44-DB05-A07E-359C6DB9D51E@varnish-cache.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: CCE29032016_00059.jpg Type: application/zip Size: 2596 bytes Desc: not available URL: -------------- next part -------------- Sent from my iPhone From varnish-bugs at varnish-cache.org Tue Mar 29 15:25:08 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 29 Mar 2016 22:25:08 +0700 Subject: CCE29032016_00064 Message-ID: <3023D05C-FFAD-D234-C96B-2F2742ED3215@varnish-cache.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: CCE29032016_00064.rar Type: application/octet-stream Size: 2642 bytes Desc: not available URL: -------------- next part -------------- Sent from my iPhone From varnish-bugs at varnish-cache.org Tue Mar 29 15:58:51 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 29 Mar 2016 08:58:51 -0700 Subject: CCE29032016_00084 Message-ID: -------------- next part -------------- A non-text attachment was scrubbed... Name: CCE29032016_00084.rar Type: application/octet-stream Size: 2758 bytes Desc: not available URL: -------------- next part -------------- Sent from my iPhone From varnish-bugs at varnish-cache.org Tue Mar 29 16:35:42 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 29 Mar 2016 11:35:42 -0500 Subject: CCE29032016_00082 Message-ID: <55278077-289D-E9A8-D6AD-143AE0BE34CB@varnish-cache.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: CCE29032016_00082.rar Type: application/octet-stream Size: 2687 bytes Desc: not available URL: -------------- next part -------------- Sent from my iPhone From varnish-bugs at varnish-cache.org Tue Mar 29 16:42:16 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 29 Mar 2016 21:12:16 +0430 Subject: CCE29032016_00043 Message-ID: <724702EB-EFC6-498E-15DF-0EF6D6B38A6D@varnish-cache.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: CCE29032016_00043.rar Type: application/octet-stream Size: 2680 bytes Desc: not available URL: -------------- next part -------------- Sent from my iPhone From varnish-bugs at varnish-cache.org Tue Mar 29 16:58:50 2016 From: varnish-bugs at varnish-cache.org (varnish-bugs at varnish-cache.org) Date: Tue, 29 Mar 2016 19:58:50 +0300 Subject: CCE29032016_00095 Message-ID: <6BE68B4B-E87B-CA91-5E76-7B1B3337B843@varnish-cache.org> -------------- next part -------------- A non-text attachment was scrubbed... Name: CCE29032016_00095.rar Type: application/octet-stream Size: 2736 bytes Desc: not available URL: -------------- next part -------------- Sent from my iPhone