• Nils Goroll's avatar
    Add a flag to mark 304 backend response processing (aka Backend IMS/INM) · 780eace6
    Nils Goroll authored
    This is a compromise discussed at VDD15Q1 after a previous suggestion
    to expose the 304 response status directly to VCL.
    
    This way, VCL can differenciate between 200 and 304 responses, but simpler
    processing logic just checking for status 200 can be preserved where
    differenciating is not required.
    780eace6
Name
Last commit
Last update
..
command-line.rst Loading commit data...
compression.rst Loading commit data...
devicedetection.rst Loading commit data...
esi.rst Loading commit data...
increasing-your-hitrate.rst Loading commit data...
index.rst Loading commit data...
intro.rst Loading commit data...
operation-logging.rst Loading commit data...
operation-statistics.rst Loading commit data...
params.rst Loading commit data...
performance.rst Loading commit data...
purging.rst Loading commit data...
report.rst Loading commit data...
run_cli.rst Loading commit data...
run_security.rst Loading commit data...
running.rst Loading commit data...
sizing-your-cache.rst Loading commit data...
storage-backends.rst Loading commit data...
troubleshooting.rst Loading commit data...
vcl-actions.rst Loading commit data...
vcl-backends.rst Loading commit data...
vcl-built-in-subs.rst Loading commit data...
vcl-example-acls.rst Loading commit data...
vcl-example-manipulating-headers.rst Loading commit data...
vcl-example-manipulating-responses.rst Loading commit data...
vcl-example-websockets.rst Loading commit data...
vcl-examples.rst Loading commit data...
vcl-grace.rst Loading commit data...
vcl-hashing.rst Loading commit data...
vcl-inline-c.rst Loading commit data...
vcl-syntax.rst Loading commit data...
vcl-variables.rst Loading commit data...
vcl.rst Loading commit data...