Switch branches/tags
varnish-6.1.1 varnish-6.1.0 varnish-6.0.2 varnish-6.0.1 varnish-6.0.0 varnish-5.2.1 varnish-5.2.0 varnish-5.2.0-rc2 varnish-5.2.0-rc1 varnish-5.1.3 varnish-5.1.2 varnish-5.1.1 varnish-5.1.0 varnish-5.0.0 varnish-5.0.0-beta1 varnish-4.1.10 varnish-4.1.9 varnish-4.1.8 varnish-4.1.7 varnish-4.1.6 varnish-4.1.5 varnish-4.1.5-beta2 varnish-4.1.5-beta1 varnish-4.1.4 varnish-4.1.4-beta3 varnish-4.1.4-beta2 varnish-4.1.4-beta1 varnish-4.1.3 varnish-4.1.3-beta2 varnish-4.1.3-beta1 varnish-4.1.2 varnish-4.1.2-beta2 varnish-4.1.2-beta1 varnish-4.1.1 varnish-4.1.1-beta2 varnish-4.1.1-beta1 varnish-4.1.0 varnish-4.1.0-tp1 varnish-4.1.0-beta1 varnish-4.0.5 varnish-4.0.4 varnish-4.0.4-beta1 varnish-4.0.3 varnish-4.0.3-rc3 varnish-4.0.3-rc2 varnish-4.0.3-rc2-proper varnish-4.0.3-rc1 varnish-4.0.2 varnish-4.0.2-rc1 varnish-4.0.1 varnish-4.0.0 varnish-4.0.0-tp2 varnish-4.0.0-tp1 varnish-4.0.0-beta1 varnish-3.0.7 varnish-3.0.7-rc1 varnish-3.0.6 varnish-3.0.6-proper varnish-3.0.5 varnish-3.0.4 varnish-3.0.4-rc1 varnish-3.0.3 varnish-3.0.3-rc1 varnish-3.0.2 varnish-3.0.2-rc1 varnish-3.0.1 varnish-3.0.1-rc1 varnish-3.0.0 varnish-3.0.0-beta2 varnish-3.0.0-beta1 varnish-2.1.5 varnish-2.1.4 varnish-2.1.3 varnish-2.1.2 varnish-2.1.1 varnish-2.1.0 varnish-2.0.6 varnish-2.0.5 varnish-2.0.4 varnish-2.0.3 varnish-2.0.2 varnish-2.0.1 varnish-2.0 varnish-2.0-tp2 varnish-2.0-tp1 varnish-2.0-rc1 varnish-2.0-beta2 varnish-2.0-beta1 varnish-1.1.2 varnish-1.1.1 varnish-1.1 varnish-1.0.4 varnish-1.0.3 varnish-1.0.2 varnish-1.0.1 varnish-1.0 varnish-0.9.1 varnish-0.9 live-test-1 key_header03
Nothing to show
Commits on Nov 2, 2018
Commits on Oct 30, 2018
  1. Indent continuations

    Dridi committed Oct 30, 2018
  2. Missing line continuation

    Dridi committed Oct 30, 2018
Commits on Oct 17, 2018
Commits on Oct 5, 2018
  1. Fix assertion for PUSH_PROMISE frames

    Dridi committed Oct 5, 2018
    r2 can be either null or not.
    Test case by @daghf
    Refs #2781
  2. Hardening of the h2_frame_f callbacks

    Dridi committed Oct 5, 2018
    And by the way, they are known as h2_rxframe_f these days!
    Refs #2781
Commits on Sep 28, 2018
  1. VSC_Arg succeeds with non-zero

    Dridi committed Sep 28, 2018
    Fixes #2787
Commits on Sep 17, 2018
  1. Clarify what Debug means

    Dridi committed Sep 17, 2018
  2. s/belive/believe/

    Dridi committed Sep 17, 2018
Commits on Sep 12, 2018
  1. Typo

    Dridi committed Sep 12, 2018
  2. Typo

    Dridi committed Sep 12, 2018
Commits on Sep 11, 2018
  1. New feature isn't that new

    Dridi committed Sep 11, 2018
Commits on Sep 4, 2018
Commits on Aug 28, 2018
  1. Whitespace OCD

    Dridi committed Aug 28, 2018
Commits on Aug 27, 2018
  1. Whitespace OCD

    Dridi committed Aug 27, 2018
Commits on Aug 25, 2018
  1. Constify

    Dridi committed Aug 25, 2018
Commits on Jul 4, 2018
  1. varnishtop -d does not exit by itself

    Dridi committed Jul 4, 2018
    Unless -1 is used too, but -1 already implies -d so it doesn't really
    Fixes #2721
  2. Revert "Terminate varnishtop -d automatically"

    Dridi committed Jul 4, 2018
    This reverts commit d1b78e8.
    The problem is that upon exiting the screen is likely to be cleared on
    most terminals (not the one we embed in varnishtest for example) so it
    doesn't give any chance to the user to read the output.
    The consensus is to restore the previous behavior and fix the manual
    Refs #2721
Commits on May 28, 2018
  1. Some varnishtop -f coverage

    Dridi committed May 22, 2018
  2. Remove arbitrary 1.0 threshold in varnishtop -1

    Dridi committed May 22, 2018
    With that both -d and -1 options report the same output, with the former
    limited to the terminal height. While this increases the risk of "never
    ending" dumps of log records showing only once, the assumption is that
    varnishtop is useful when someone is looking for something in particular.
    Restricting the output to the records someone is interested in mitigates
    the risk.
    Fixes #2686
  3. Terminate varnishtop -d automatically

    Dridi committed May 22, 2018
    Following the documentation, the -d option implies that once processing
    is done the process should exit. We give it the time to do one last
    refresh of the screen in curses mode.
    Refs #2686
Commits on May 25, 2018
Commits on May 21, 2018
Commits on May 2, 2018
  1. Drop VALID_OBJ for GCC

    Dridi committed May 2, 2018
    It complains that &pfh_vut is never NULL...
  2. Align the lifetime of the PID file to the VUT process

    Dridi committed May 2, 2018
    For out-of-tree code that may set up multiple VUTs in a single process,
    we don't want the VUT that initialized a PID file to remove it if it
    finishes before other VUTs.
    A global pseudo-VUT is introduced to keep track of the PID file and
    the error callback in order to use them in the atexit(3) callback.
    Original test case by Geoff, slightly modified.
    Closes #2651
  3. Only handle signals if we still have a VUT

    Dridi committed May 2, 2018
    This can happen if a signal is caught after `VUT_Fini` was called, but
    at this point we should no longer manipulate the VUT being dismantled.
    Original test case by Geoff, slightly modified.
    Closes #2650
  4. Simplify o5.vtc

    Dridi committed May 2, 2018
  5. Whitespace OCD

    Dridi committed May 2, 2018
Commits on Mar 26, 2018
  1. Incomplete condition

    Dridi committed Mar 26, 2018
Commits on Mar 15, 2018
  1. New VARNISH_COUNTERS macro for varnish.m4

    Dridi committed Mar 15, 2018
    Initially written and tested for Varnish 5.2, but not included then
    because VMODs weren't allowed custom counters yet. Tested again with
    success for Varnish 6.0 and documented.
Commits on Mar 13, 2018
  1. Install cache/cache_varnishd.h as part of $ABI strict

    Dridi committed Mar 13, 2018
    This removes the need for non-VRT VMODs to require a Varnish source tree
    to build, especially since varnish.m4 only supports Varnish installations
    today and would leave VMOD authors on their own in order to build from
    a source tree. Since $ABI defaults to strict, any VMOD author actively
    choosing vrt compliance is responsible for ensuring it only uses blessed
    In our official packages, they land in the varnish-dev deb and the
    varnish-devel RPM:
        $ rpm --query --package --list varnish-trunk-1.el7.x86_64.rpm |
        > grep cache_varnishd.h
        $ rpm --query --package --list varnish-devel-trunk-1.el7.x86_64.rpm |
        > grep cache_varnishd.h
    You will have to trust me for the Debs as it's a bit cumbersome for me to
    build them locally.