April 2009 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Thu Apr 2 11:12:39 CEST 2009
Ending: Thu Apr 30 13:15:03 CEST 2009
Messages: 81

• [Varnish] #225: VCL: Allow "Expires" time to be easily specified / calculated   Varnish
• [Varnish] #272: Assert error in vca_acct(), cache_acceptor.c line 173   Varnish
• [Varnish] #329: Increase cli_timeout   Varnish
• [Varnish] #351: v00017.vtc, v00018.vtc and v00019.vtc fails on ppc64   Varnish
• [Varnish] #360: Cannot create temp file on startup   Varnish
• [Varnish] #364: Panic message: Missing errorhandling code in cnt_lookup(), cache_center.c line 606:   Varnish
• [Varnish] #378: unresonable varnish free smf number   Varnish
• [Varnish] #379: The varnish have no response most of the time , is it the bug?   Varnish
• [Varnish] #383: Unexplained vcl behaivior maybe header related to header modify   Varnish
• [Varnish] #424: test c00014 failure on RHEL 4u7 build   Varnish
• [Varnish] #431: Crash in fetch   Varnish
• [Varnish] #444: allow to handle non-GET req in vcl_miss   Varnish
• [Varnish] #453: Assert error in WS_Release(), cache_ws.c line 170   Varnish
• [Varnish] #455: Make HTTP_HDR_MAX a ./configure option   Varnish
• [Varnish] #463: varnish returns no content on error 403/404 from thttpd backend   Varnish
• [Varnish] #465: regsub seems no use in sub_recv as a hash key   Varnish
• [Varnish] #467: prevent percent-aspects of munin plugin from scaling   Varnish
• [Varnish] #481: Retain information about backends post-vbe_conn destruction for use in VCL   Varnish
• [Varnish] #481: Retain information about backends post-vbe_conn destruction for use in VCL   Varnish
• [Varnish] #482: Polling broken on Solaris?   Varnish
• [Varnish] #482: Polling broken on Solaris?   Varnish
• [Varnish] #482: Polling broken on Solaris?   Varnish
• [Varnish] #483: Varnishstat should show the number of healthy / sick backends   Varnish
• [Varnish] #484: Dum5apr2009   Varnish
• [Varnish] #485: Virtualhost logging for varnishncsa   Varnish
• [Varnish] #486: link failure with --as-needed   Varnish
• [Varnish] #486: link failure with --as-needed   Varnish
• [Varnish] #487: Varnish crashes on Panic message: Missing errorhandling code in WS_Reserve(), cache_ws.c line 159   Varnish
• [Varnish] #487: Varnish crashes on Panic message: Missing errorhandling code in WS_Reserve(), cache_ws.c line 159   Varnish
• [Varnish] #487: Varnish crashes on Panic message: Missing errorhandling code in WS_Reserve(), cache_ws.c line 159   Varnish
• [Varnish] #488: child process restart with "Missing errorhandling code in sma_alloc()" error   Varnish
• [Varnish] #488: child process restart with "Missing errorhandling code in sma_alloc()" error   Varnish
• [Varnish] #489: Assert error in BAN_CheckObject()   Varnish
• [Varnish] #490: Hash based director   Varnish
• [Varnish] #490: Hash based director   Varnish
• [Varnish] #491: Crash in 2.0.4   Varnish
• [Varnish] #492: cache_waiter_epoll.c / cache_acceptor_epoll.c entire rewritten for Linux boxes better performance   Varnish
• [Varnish] #492: cache_waiter_epoll.c / cache_acceptor_epoll.c entire rewritten for Linux boxes better performance   Varnish
• [Varnish] #492: cache_waiter_epoll.c / cache_acceptor_epoll.c entire rewritten for Linux boxes better performance   Varnish
• [Varnish] #492: cache_waiter_epoll.c / cache_acceptor_epoll.c entire rewritten for Linux boxes better performance   Varnish
• [Varnish] #493: sgdfjgh   Varnish
• [Varnish] #493: sgdfjgh   Varnish
• [Varnish] #493: sgdfjgh   Varnish
• [Varnish] #493: sgdfjgh   Varnish
• [Varnish] #493: varnish-tools/regress broken   Varnish
• [Varnish] #493: varnish-tools/regress broken   Varnish
• [Varnish] #494: When backend server continues a header line with \n\t rather than \r\n\t remove only removes first line of header   Varnish
• [Varnish] #494: When backend server continues a header line with \n\t rather than \r\n\t remove only removes first line of header   Varnish
• [Varnish] #494: When backend server continues a header line with \n\t rather than \r\n\t remove only removes first line of header   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #495: HTTP/1.0 or 'Connection: closed' backend race condition   Varnish
• [Varnish] #496: 才   Varnish
• Re: [Varnish] #496: 才   Varnish
• [Varnish] #497: Overflow in vrt_assemble_string   Varnish
• [Varnish] #498: khj   Varnish
• [Varnish] #498: Segfault with weird headers   Varnish
• [Varnish] #498: Segfault with weird headers   Varnish
• [Varnish] #498: Segfault with weird headers   Varnish
• [Varnish] #498: 小地方见过付款计划   Varnish
• [Varnish] #499: Request for Wiki Editing Bits   Varnish
• [Varnish] #499: Request for Wiki Editing Bits   Varnish
• [Varnish] #500: fhfgkh   Varnish
• [Varnish] #500: fhfgkh   Varnish
• [Varnish] #500: Problem ACL in purge mode.   Varnish
• [Varnish] #500: Problem ACL in purge mode.   Varnish
• [Varnish] #500: Problem ACL in purge mode.   Varnish
• [Varnish] #500: Problem ACL in purge mode.   Varnish
• [Varnish] #500: Problem ACL in purge mode.   Varnish
• [Varnish] #501: eyrt   Varnish
• [Varnish] #501: Stats variable to monitor how many threads are actually doing something (n_wrk_busy): busy threads monitoring   Varnish
• [Varnish] #501: Stats variable to monitor how many threads are actually doing something (n_wrk_busy): busy threads monitoring   Varnish
• [Varnish] #501: Stats variable to monitor how many threads are actually doing something (n_wrk_busy): busy threads monitoring   Varnish
• [Varnish] #501: Stats variable to monitor how many threads are actually doing something (n_wrk_busy): busy threads monitoring   Varnish

Last message date: Thu Apr 30 13:15:03 CEST 2009
Archived on: Wed Apr 23 00:58:21 CEST 2014

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...