Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
V
varnish-cache
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
varnishcache
varnish-cache
Commits
650b78b7
Commit
650b78b7
authored
Mar 07, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update docs for *.uncacheable in generate.py regarding hit-for-miss/-pass
parent
856d5627
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
4 deletions
+5
-4
generate.py
lib/libvcc/generate.py
+5
-4
No files found.
lib/libvcc/generate.py
View file @
650b78b7
...
...
@@ -452,8 +452,8 @@ sp_variables = [
(
'backend'
,
),
(),
"""
Indicates whether this request is uncacheable due
to a pass in the client side or a hit on an
existing
uncacheable object (aka hit-for-pass)
.
to a pass in the client side or a hit on an
hit-for-pass
object
.
"""
),
(
'bereq.connect_timeout'
,
...
...
@@ -578,7 +578,7 @@ sp_variables = [
Inherited from bereq.uncacheable, see there.
Setting this variable makes the object uncacheable, which may
get stored as a hit-for-
pa
ss object in the cache.
get stored as a hit-for-
mi
ss object in the cache.
Clearing the variable has no effect and will log the warning
"Ignoring attempt to reset beresp.uncacheable".
...
...
@@ -727,7 +727,8 @@ sp_variables = [
'BOOL'
,
(
'deliver'
,),
(),
"""
Whether the object is uncacheable (pass or hit-for-pass).
Whether the object is uncacheable (pass, hit-for-pass or
hit-for-miss).
"""
),
(
'resp'
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment