Commit f52d6645 authored by Dridi Boukelmoune's avatar Dridi Boukelmoune

doc: Remove trailing blanks

parent e0624cda
......@@ -83,7 +83,7 @@ that to a German Engineer...
Nils Goroll from UPLEX didn't quite say *"Halten Sie Mein Bier…"*,
but he did produce a VCL workaround right away, once again using
the inline-C capability, to frob things which are normally
the inline-C capability, to frob things which are normally
"No User Serviceable Parts Behind This Door".
Bravo Nils!
......
......@@ -14,7 +14,7 @@ I'm old enough to remember `HOSTS.TXT` and the introduction of the DNS system.
Those were the days when you got a class B network by sending a
polite letter to California, getting a polite letter back, and then,
some months later, when
`RFC1166 INTERNET NUMBERS <https://tools.ietf.org/html/rfc1166>`_
`RFC1166 INTERNET NUMBERS <https://tools.ietf.org/html/rfc1166>`_
arrived with in semi-annual packet of printed RFCs,
find out that letter had at typo and you had configured all of
the European Parliaments 1200 computers on 136.172/16 instead of
......@@ -43,7 +43,7 @@ why `ping 0x7f000001` becomes `127.0.0.1` and `0127.0.0.1`
becomes `87.0.0.1`.
If you read the manual page for `getaddrinfo(3)` you will find
that it does not tell you that, it merely says it
that it does not tell you that, it merely says it
`conforms to IEEE Std 1001`.
But everybody knew what that was back in 1990, and nobody had firewalls
......@@ -74,7 +74,7 @@ That has just become CVE-2021-29418 and CVE-2021-28918 and will
probably become a dozen more, once the CVE-trophy-hunters go to town.
All IP number strings enter Varnish from trusted points, either
as command line arguments (`-a`, `-b`, `-M` etc.),
as command line arguments (`-a`, `-b`, `-M` etc.),
in the VCL source (`backend`, `acl` etc.) or as PROXYv1 header
strings from the TLS-stripper in front of Varnish.
......
......@@ -32,7 +32,7 @@ also using their own HDLC frame layout.
you have used it: That was the hot way to do error-correction on
modems, when dialing into a BBS or ISP in the 1990ies.
I guess I should say "legacy-modems" ?
I guess I should say "legacy-modems" ?
Big-endianess, storing the bytes the sensible way for hex-dumps, is
rapidly becoming legacy, as the final old HP and SUN irons are
......
......@@ -216,7 +216,7 @@ I took myself out of the game:
QcQAn18fGLT4Lx2ACBivtk5wEFy6fUcu
=3V52
-----END PGP SIGNATURE-----
--
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
......
......@@ -61,7 +61,7 @@ Logging and monitoring
VarnishNCSA - Logging in NCSA format <varnishncsa>
VarnishHist - Realtime reponse histogram display <varnishhist>
VarnishTop - Realtime activity display <varnishtop>
Counters and statistics
-----------------------
......
......@@ -6,7 +6,7 @@
.. _ref-shell_tricks:
%%%%%%%%%%%%
Shell Tricks
Shell Tricks
%%%%%%%%%%%%
All the varnish programs can be invoked with the single
......
......@@ -20,7 +20,7 @@ HTTP accelerator daemon
SYNOPSIS
========
varnishd
varnishd
[-a [name=][listen_address[,PROTO]]
[-b [host[:port]|path]]
[-C]
......
......@@ -52,7 +52,7 @@ IPv4/IPv6 address or a domain name which resolves to *at most*
one IPv4 and one IPv6 address::
.host = "127.0.0.1";
.host = "[::1]:8080";
.host = "example.com:8081";
......
......@@ -140,7 +140,7 @@ is considered fully healthy.
An additional ``.initial`` fills that many "happy" entries in the
shift register when the VCL is loaded, so that backends can quickly
become healthy, even if their health is normally considered over
become healthy, even if their health is normally considered over
many samples::
.interval = 1s;
......
......@@ -76,21 +76,21 @@ status message.
SEE ALSO
========
* :ref:`varnishd(1)`
* :ref:`vcl(7)`
HISTORY
=======
VCL was developed by Poul-Henning Kamp in cooperation with Verdens
Gang AS, Redpill Linpro and Varnish Software. This manual page is
written by Per Buer, Poul-Henning Kamp, Martin Blix Grydeland,
Kristian Lyngstøl, Lasse Karstensen and others.
COPYRIGHT
=========
This document is licensed under the same license as Varnish
itself. See LICENSE for details.
......
......@@ -19,7 +19,7 @@ Varnish, and it is a pretty apt metafor::
┌─────┐ ╔═════════╗ ┌─────┐ ┌─────────┐ ┌─────────┐│┘
│ app │ --- ║ Network ║ -- │ TLS │ -- │ Varnish │ -- │ Backend │┘
└─────┘ ╚═════════╝ └─────┘ └─────────┘ └─────────┘
/
/
┌────────────┐
│ API-client │
└────────────┘
......@@ -65,7 +65,7 @@ be examined and monitored in real time or recorded for later use
in native or NCSA format, and when we say 'everything' we mean
*everything*::
* << Request >> 318737
* << Request >> 318737
- Begin req 318736 rxreq
- Timestamp Start: 1612787907.221931 0.000000 0.000000
- Timestamp Req: 1612787907.221931 0.000000 0.000000
......
......@@ -26,19 +26,19 @@ with command-completion, command-history and other comforts:
.. code-block:: text
critter phk> ./varnishadm
200
critter phk> ./varnishadm
200
-----------------------------
Varnish Cache CLI 1.0
-----------------------------
FreeBSD,13.0-CURRENT,amd64,-jnone,-sdefault,-sdefault,-hcritbit
varnish-trunk revision 2bd5d2adfc407216ebaa653fae882d3c8d47f5e1
Type 'help' for command list.
Type 'quit' to close CLI session.
Type 'start' to launch worker process.
varnish>
varnish>
The CLI always returns a three digit status code to tell how things went.
......
......@@ -5,7 +5,7 @@
.. _dp_vcl_resp_status:
Using extra digits in resp.status
Using extra digits in resp.status
=================================
In Varnish the ``.status`` variables can hold more than three
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment