[4.0] 0077964 document bereq.uncacheable and beresp.uncacheable
Lasse Karstensen
lkarsten at varnish-software.com
Thu Jan 15 16:35:39 CET 2015
commit 00779649cb758f0cbfad3c509f1a1ffe43df31fc
Author: Nils Goroll <nils.goroll at uplex.de>
Date: Thu Oct 9 17:00:10 2014 +0200
document bereq.uncacheable and beresp.uncacheable
diff --git a/lib/libvcc/generate.py b/lib/libvcc/generate.py
index 9af3420..44c0c55 100755
--- a/lib/libvcc/generate.py
+++ b/lib/libvcc/generate.py
@@ -360,6 +360,16 @@ sp_variables = [
'BOOL',
( 'backend', ),
( 'backend', ), """
+ Indicates whether the object requested from the backend is
+ going to be uncacheable - either because the request was an
+ explicit pass from the client side or a hit on an uncacheable
+ ("hit for pass") object.
+
+ Setting this variable in vcl_backend_fetch makes the object
+ uncacheable.
+
+ Clearing the variable has no effect and will log the warning
+ "Ignoring attempt to reset bereq.uncacheable".
"""
),
('bereq.connect_timeout',
@@ -461,6 +471,13 @@ sp_variables = [
'BOOL',
( 'backend_response', 'backend_error'),
( 'backend_response', 'backend_error'), """
+ Inherited from bereq.uncacheable, see there.
+
+ Setting this variable makes the object uncacheable, which may
+ get stored as a hit-for-pass object in the cache.
+
+ Clearing the variable has no effect and will log the warning
+ "Ignoring attempt to reset beresp.uncacheable".
"""
),
('beresp.ttl',
More information about the varnish-commit
mailing list