[4.0] 74cae57 make bereq.uncacheable read-only outside backend_fetch

Lasse Karstensen lkarsten at varnish-software.com
Thu Jan 15 16:35:39 CET 2015

commit 74cae57337794b51b53f358fdf893bd54d181b65
Author: Nils Goroll <nils.goroll at uplex.de>
Date:   Thu Oct 9 17:28:20 2014 +0200

    make bereq.uncacheable read-only outside backend_fetch
    Writing to bereq.uncacheable in backend_response and backend_error would only
    make sense in the context of a retry. In most real world cases, writing to
    be*resp*.uncacheable would be intended in backend_response and backend_error.

diff --git a/lib/libvcc/generate.py b/lib/libvcc/generate.py
index 5ba1405..10ab8d3 100755
--- a/lib/libvcc/generate.py
+++ b/lib/libvcc/generate.py
@@ -359,7 +359,7 @@ sp_variables = [
 		( 'backend', ),
-		( 'backend', ), """
+		( 'backend_fetch', ), """
 		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

More information about the varnish-commit mailing list