• Nils Goroll's avatar
    streamline ttl handling for passes · d9b09191
    Nils Goroll authored
    It was counter-intuitive that, for pass objects, we logged the
    parsed TTL when in fact the ttl visible from vcl was always 0.
    In the builtin.vcl the Hit-For-Pass check was also called
    for objects already classified as uncacheable.
    
    Now, for passes, we
    
    - do not parse Cache-Control / Expires
      - and, consequently, do not log TTL RFC
    - do not call the hfp-code in builtin.vcl
      - and, consequently, do not log TTL VCL
    
    Reflect this in b2.vtc
    d9b09191
Name
Last commit
Last update
..
tests Loading commit data...
tests.disabled Loading commit data...
Makefile.am Loading commit data...
Makefile.phk Loading commit data...
flint.lnt Loading commit data...
flint.sh Loading commit data...
programs.h Loading commit data...
vmods.h Loading commit data...
vtc.c Loading commit data...
vtc.h Loading commit data...
vtc_barrier.c Loading commit data...
vtc_client.c Loading commit data...
vtc_http.c Loading commit data...
vtc_log.c Loading commit data...
vtc_logexp.c Loading commit data...
vtc_main.c Loading commit data...
vtc_process.c Loading commit data...
vtc_proxy.c Loading commit data...
vtc_server.c Loading commit data...
vtc_varnish.c Loading commit data...
witness.py Loading commit data...