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
5721b7c0
Commit
5721b7c0
authored
Apr 23, 2020
by
Pierre Grimaud
Committed by
Dridi Boukelmoune
Apr 23, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos
parent
95abb73e
Changes
13
Show whitespace changes
Inline
Side-by-side
Showing
13 changed files
with
15 additions
and
15 deletions
+15
-15
CONTRIBUTING
CONTRIBUTING
+1
-1
cache_fetch_proc.c
bin/varnishd/cache/cache_fetch_proc.c
+1
-1
cache_panic.c
bin/varnishd/cache/cache_panic.c
+1
-1
cache_tcp_pool.h
bin/varnishd/cache/cache_tcp_pool.h
+1
-1
hash_critbit.c
bin/varnishd/hash/hash_critbit.c
+1
-1
mgt_jail.c
bin/varnishd/mgt/mgt_jail.c
+1
-1
mgt_param_tcp.c
bin/varnishd/mgt/mgt_param_tcp.c
+1
-1
varnish-cli.rst
doc/sphinx/reference/varnish-cli.rst
+1
-1
varnishtest.rst
doc/sphinx/reference/varnishtest.rst
+2
-2
devicedetection.rst
doc/sphinx/users-guide/devicedetection.rst
+1
-1
esi.rst
doc/sphinx/users-guide/esi.rst
+1
-1
increasing-your-hitrate.rst
doc/sphinx/users-guide/increasing-your-hitrate.rst
+1
-1
storage-backends.rst
doc/sphinx/users-guide/storage-backends.rst
+2
-2
No files found.
CONTRIBUTING
View file @
5721b7c0
...
@@ -25,5 +25,5 @@ Github pull requests
...
@@ -25,5 +25,5 @@ Github pull requests
Pull requests are handled like other tickets.
Pull requests are handled like other tickets.
Trivial pull requests (fix typos, etc) are welcomed, but they may be commited
Trivial pull requests (fix typos, etc) are welcomed, but they may be commit
t
ed
by a core team member and the author credited in the commit message.
by a core team member and the author credited in the commit message.
bin/varnishd/cache/cache_fetch_proc.c
View file @
5721b7c0
...
@@ -41,7 +41,7 @@ static unsigned fetchfrag;
...
@@ -41,7 +41,7 @@ static unsigned fetchfrag;
/*--------------------------------------------------------------------
/*--------------------------------------------------------------------
* We want to issue the first error we encounter on fetching and
* We want to issue the first error we encounter on fetching and
* supress the rest. This function does that.
* sup
p
ress the rest. This function does that.
*
*
* Other code is allowed to look at busyobj->fetch_failed to bail out
* Other code is allowed to look at busyobj->fetch_failed to bail out
*
*
...
...
bin/varnishd/cache/cache_panic.c
View file @
5721b7c0
...
@@ -806,7 +806,7 @@ pan_ic(const char *func, const char *file, int line, const char *cond,
...
@@ -806,7 +806,7 @@ pan_ic(const char *func, const char *file, int line, const char *cond,
VSL_Flush
(
bo
->
vsl
,
0
);
VSL_Flush
(
bo
->
vsl
,
0
);
VMOD_Panic
(
pan_vsb
);
VMOD_Panic
(
pan_vsb
);
}
else
{
}
else
{
VSB_cat
(
pan_vsb
,
"Feature short panic supressed details.
\n
"
);
VSB_cat
(
pan_vsb
,
"Feature short panic sup
p
ressed details.
\n
"
);
}
}
VSB_cat
(
pan_vsb
,
"
\n
"
);
VSB_cat
(
pan_vsb
,
"
\n
"
);
VSB_putc
(
pan_vsb
,
'\0'
);
/* NUL termination */
VSB_putc
(
pan_vsb
,
'\0'
);
/* NUL termination */
...
...
bin/varnishd/cache/cache_tcp_pool.h
View file @
5721b7c0
...
@@ -76,7 +76,7 @@ void VTP_Rel(struct tcp_pool **);
...
@@ -76,7 +76,7 @@ void VTP_Rel(struct tcp_pool **);
int
VTP_Open
(
struct
tcp_pool
*
,
vtim_dur
tmo
,
const
void
**
,
int
*
);
int
VTP_Open
(
struct
tcp_pool
*
,
vtim_dur
tmo
,
const
void
**
,
int
*
);
/*
/*
* Open a new connection and return the adress used.
* Open a new connection and return the ad
d
ress used.
* errno will be returned in the last argument.
* errno will be returned in the last argument.
*/
*/
...
...
bin/varnishd/hash/hash_critbit.c
View file @
5721b7c0
...
@@ -188,7 +188,7 @@ hcb_crit_bit(const uint8_t *digest, const struct objhead *oh2, struct hcb_y *y)
...
@@ -188,7 +188,7 @@ hcb_crit_bit(const uint8_t *digest, const struct objhead *oh2, struct hcb_y *y)
/*---------------------------------------------------------------------
/*---------------------------------------------------------------------
* Unless we have the lock, we need to be very careful about pointer
* Unless we have the lock, we need to be very careful about pointer
* references into the tree, we cannot trust things to be the same
* references into the tree, we cannot trust things to be the same
* in two conse
q
utive memory accesses.
* in two conse
c
utive memory accesses.
*/
*/
static
struct
objhead
*
static
struct
objhead
*
...
...
bin/varnishd/mgt/mgt_jail.c
View file @
5721b7c0
...
@@ -101,7 +101,7 @@ VJ_Init(const char *j_arg)
...
@@ -101,7 +101,7 @@ VJ_Init(const char *j_arg)
if
(
av
[
0
]
!=
NULL
)
if
(
av
[
0
]
!=
NULL
)
ARGV_ERR
(
"-j argument: %s
\n
"
,
av
[
0
]);
ARGV_ERR
(
"-j argument: %s
\n
"
,
av
[
0
]);
if
(
av
[
1
]
==
NULL
)
if
(
av
[
1
]
==
NULL
)
ARGV_ERR
(
"-j argument is em
tp
y
\n
"
);
ARGV_ERR
(
"-j argument is em
pt
y
\n
"
);
vjt
=
MGT_Pick
(
vj_choice
,
av
[
1
],
"jail"
);
vjt
=
MGT_Pick
(
vj_choice
,
av
[
1
],
"jail"
);
CHECK_OBJ_NOTNULL
(
vjt
,
JAIL_TECH_MAGIC
);
CHECK_OBJ_NOTNULL
(
vjt
,
JAIL_TECH_MAGIC
);
(
void
)
vjt
->
init
(
av
+
2
);
(
void
)
vjt
->
init
(
av
+
2
);
...
...
bin/varnishd/mgt/mgt_param_tcp.c
View file @
5721b7c0
...
@@ -30,7 +30,7 @@
...
@@ -30,7 +30,7 @@
*
*
* Parameters related to TCP keepalives are not universally available
* Parameters related to TCP keepalives are not universally available
* as socket options, and probing for system-wide defaults more appropriate
* as socket options, and probing for system-wide defaults more appropriate
* than our own involves slightly too much grunt-work to be neglible
* than our own involves slightly too much grunt-work to be negli
gi
ble
* so we sequestrate that code here.
* so we sequestrate that code here.
*/
*/
...
...
doc/sphinx/reference/varnish-cli.rst
View file @
5721b7c0
...
@@ -213,7 +213,7 @@ Backend Pattern
...
@@ -213,7 +213,7 @@ Backend Pattern
A backend pattern can be a backend name or a combination of a VCL name
A backend pattern can be a backend name or a combination of a VCL name
and backend name in "VCL.backend" format. If the VCL name is omitted,
and backend name in "VCL.backend" format. If the VCL name is omitted,
the active VCL is assumed. Partial matching on the backend and VCL
the active VCL is assumed. Partial matching on the backend and VCL
names is supported using shell-style wilcards, e.g. asterisk (*).
names is supported using shell-style wil
d
cards, e.g. asterisk (*).
Examples::
Examples::
...
...
doc/sphinx/reference/varnishtest.rst
View file @
5721b7c0
...
@@ -144,9 +144,9 @@ they look roughly like this::
...
@@ -144,9 +144,9 @@ they look roughly like this::
exec varnishd [varnishtest -p params] [testing params] [vtc -arg params]
exec varnishd [varnishtest -p params] [testing params] [vtc -arg params]
Parameters you define with ``varnishtest -p`` may be overriden by
Parameters you define with ``varnishtest -p`` may be overrid
d
en by
parameters needed by ``varnishtest`` to run properly, and they may in
parameters needed by ``varnishtest`` to run properly, and they may in
turn be overriden by parameters set in test scripts.
turn be overrid
d
en by parameters set in test scripts.
There's also a special mode in which ``varnishtest`` builds itself a
There's also a special mode in which ``varnishtest`` builds itself a
PATH and a *vmod_path* in order to find Varnish binaries (programs and
PATH and a *vmod_path* in order to find Varnish binaries (programs and
...
...
doc/sphinx/users-guide/devicedetection.rst
View file @
5721b7c0
...
@@ -55,7 +55,7 @@ Example 1: Send HTTP header to backend
...
@@ -55,7 +55,7 @@ Example 1: Send HTTP header to backend
The basic case is that Varnish adds the 'X-UA-Device' HTTP header on the backend
The basic case is that Varnish adds the 'X-UA-Device' HTTP header on the backend
requests, and the backend mentions in the response 'Vary' header that the content
requests, and the backend mentions in the response 'Vary' header that the content
is depend
a
nt on this header.
is depend
e
nt on this header.
Everything works out of the box from Varnish' perspective.
Everything works out of the box from Varnish' perspective.
...
...
doc/sphinx/users-guide/esi.rst
View file @
5721b7c0
...
@@ -98,7 +98,7 @@ Ignoring BOM in ESI objects
...
@@ -98,7 +98,7 @@ Ignoring BOM in ESI objects
~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you backend spits out a Unicode Byte-Order-Mark as the first
If you backend spits out a Unicode Byte-Order-Mark as the first
bytes of the reponse, the "<" check will fail unless you set::
bytes of the re
s
ponse, the "<" check will fail unless you set::
param.set feature +esi_remove_bom
param.set feature +esi_remove_bom
...
...
doc/sphinx/users-guide/increasing-your-hitrate.rst
View file @
5721b7c0
...
@@ -438,7 +438,7 @@ A stale object is not removed from the cache for the duration of
...
@@ -438,7 +438,7 @@ A stale object is not removed from the cache for the duration of
increase the storage requirements for your cache, but if you have the
increase the storage requirements for your cache, but if you have the
space, it might be worth it to keep stale objects that can be
space, it might be worth it to keep stale objects that can be
validated for a fairly long time. If the backend can send a 304
validated for a fairly long time. If the backend can send a 304
response long after the TTL has expired, you save bandwith on the
response long after the TTL has expired, you save bandwi
d
th on the
fetch and reduce pressure on the storage; if not, then it's no
fetch and reduce pressure on the storage; if not, then it's no
different from any other cache miss.
different from any other cache miss.
...
...
doc/sphinx/users-guide/storage-backends.rst
View file @
5721b7c0
...
@@ -99,7 +99,7 @@ Varnish will also output this message to recommend settings for using
...
@@ -99,7 +99,7 @@ Varnish will also output this message to recommend settings for using
This recommendation should be followed to achieve an optimal
This recommendation should be followed to achieve an optimal
`libumem`_ configuration for Varnish. Setting this environment
`libumem`_ configuration for Varnish. Setting this environment
variable before starting Varnish is required bec
ua
se `libumem`_ cannot
variable before starting Varnish is required bec
au
se `libumem`_ cannot
be reconfigured once loaded.
be reconfigured once loaded.
.. _libumem: http://dtrace.org/blogs/ahl/2004/07/13/number-11-of-20-libumem/
.. _libumem: http://dtrace.org/blogs/ahl/2004/07/13/number-11-of-20-libumem/
...
@@ -208,7 +208,7 @@ for transient (short lived) objects. This includes the temporary
...
@@ -208,7 +208,7 @@ for transient (short lived) objects. This includes the temporary
objects created when returning a synthetic object. By default Varnish
objects created when returning a synthetic object. By default Varnish
would use an unlimited malloc backend for this.
would use an unlimited malloc backend for this.
.. XXX: Is this another param
a
ter? In that case handled in the same manner as above? benc
.. XXX: Is this another param
e
ter? In that case handled in the same manner as above? benc
Varnish will consider an object short lived if the TTL is below the
Varnish will consider an object short lived if the TTL is below the
parameter 'shortlived'.
parameter 'shortlived'.
...
...
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