CONTENT
  • CHANGES
Szukaj
counter

#top Konfiguracja


#top Listen


Zobacz także Listen dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Listen (2.1), Listen (3.0), Listen (4.1), Listen (5.0)
Składnia: VARNISH_LISTEN_ADDRESS=0.0.0.0
Składnia: VARNISH_LISTEN_PORT=86
Składnia: DAEMON_OPTS="-a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT}"
Opis: Default address and port to bind to Blank address means all IPv4 and IPv6 interfaces, otherwise specify a host name, an IPv4 dotted quad, or an IPv6 address in brackets.

Command line arguments:
-a address:port              # HTTP listen address and port
-b address:port              # backend address and port

Manual page in man varnishd:
-a address[:port][,address[:port][...]
Listen for client requests on the specified address and port. The address can be a host name ("localhost"), an IPv4 dotted-quad ("127.0.0.1"), or an IPv6 address enclosed in square brackets ("[::1]"). If address is not specified, varnishd will listen on all available IPv4 and IPv6 interfaces. If port is not specified, the default HTTP port as listed in /etc/services is used. Multiple listening addresses and ports can be specified as a whitespace- or comma-separated list.

-b host[:port]
Use the specified host as backend server. If port is not specified, the default is 8080.

EXAMPLES
Configure variables in file /etc/sysconfig/varnish:
[...]
# Default address and port to bind to
# Blank address means all IPv4 and IPv6 interfaces, otherwise specify
# a host name, an IPv4 dotted quad, or an IPv6 address in brackets.
VARNISH_LISTEN_ADDRESS=0.0.0.0
VARNISH_LISTEN_PORT=86

# Telnet admin interface listen address and port
VARNISH_ADMIN_LISTEN_ADDRESS=127.0.0.1
VARNISH_ADMIN_LISTEN_PORT=6082

# DAEMON_OPTS is used by the init script.  If you add or remove options, make
# sure you update this section, too.
DAEMON_OPTS="-a ${VARNISH_LISTEN_ADDRESS}:${VARNISH_LISTEN_PORT} \
             -f ${VARNISH_VCL_CONF} \
             -T ${VARNISH_ADMIN_LISTEN_ADDRESS}:${VARNISH_ADMIN_LISTEN_PORT} \
             -S ${VARNISH_SECRET_FILE} \
             -t ${VARNISH_TTL} \
             -w ${VARNISH_MIN_THREADS},${VARNISH_MAX_THREADS},${VARNISH_THREAD_TIMEOUT} \
             -s ${VARNISH_STORAGE}"



#top Signature


Zobacz także Signature dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: set (2.1), set (3.0), set (4.1), set (5.0)
Składnia: set resp.http.Via = "value";
Składnia: set resp.http.X-Varnish = "value";
Opis:

EXAMPLES
set resp.http.Via = "1.1 varnish";
set resp.http.X-Varnish = "1859304392";

Zalecana konfiguracja
# zalecana konfiguracja: wyłączenie informacji o wersji serwera w nagłówkach HTTP oraz obecności serwera proxy
remove resp.http.Via;
remove resp.http.X-Varnish;



#top Timeout


Zobacz także Timeout dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID


Dokumentacja Varnish: send_timeout (2.1) | send_timeout (3.0) | send_timeout (4.1) | send_timeout (5.0)
Command line arguments: -p send_timeout=600.000
Opis: Send timeout for client connections. If the HTTP response hasn't been transmitted in this many seconds the session is closed. See setsockopt(2) under SO_SNDTIMEO for more information.

Dokumentacja Varnish: pipe_timeout (2.1) | pipe_timeout (3.0) | pipe_timeout (4.1) | pipe_timeout (5.0)
Command line arguments: -p pipe_timeout=60.000
Opis: Idle timeout for PIPE sessions. If nothing have been received in either direction for this many seconds, the session is closed.

Dokumentacja Varnish: timeout_idle (2.1) | timeout_idle (3.0) | timeout_idle (4.1) | timeout_idle (5.0)
Command line arguments: -p timeout_idle=5.000
Opis: Idle timeout for client connections. A connection is considered idle, until we have received the full request headers.

Dokumentacja Varnish: timeout_linger (2.1) | timeout_linger (3.0) | timeout_linger (4.1) | timeout_linger (5.0)
Command line arguments: -p timeout_linger=0.050
Opis: How long the worker thread lingers on an idle session before handing it over to the waiter. When sessions are reused, as much as half of all reuses happen within the first 100 msec of the previous request completing. Setting this too high results in worker threads not doing anything for their keep, setting it too low just means that more sessions take a detour around the waiter.

Dokumentacja Varnish: Backend declarations (2.1) | Backend declarations (3.0) | Backend definition (4.1) | Backend definition (5.0)
Dokumentacja Varnish: Advanced Backend config... (2.1) | Advanced Backend config... (3.0) | Backend servers(4.1) | Backend servers(5.0)
Składnia: .connect_timeout = "value";
Opis: Timeout for connections.
Składnia: .first_byte_timeout = "value";
Opis: Timeout for first byte.
Składnia: .between_bytes_timeout = "value";
Opis: Timeout between bytes.

Dokumentacja Varnish: Backend probes (2.1) | Backend probes (3.0) | Probes (4.1) | Probes (5.0)
Składnia: .attribute = "value";
Opis: Backends can be probed to see whether they should be considered healthy or not. The return status can also be checked by using req.backend.healthy .window is how many of the latest polls we examine, while .threshold is how many of those must have succeeded for us to consider the backend healthy. .initial is how many of the probes are considered good when Varnish starts - defaults to the same amount as the threshold.
Probes will query the backend for status on a regular basis and mark the backend as down it they fail. The probe named default is special and will be used for all backends which do not explicitly reference a probe.

Dokumentacja Varnish: connect_timeout (2.1) | connect_timeout (3.0) | connect_timeout (4.1) | connect_timeout (5.0)
Składnia: .bereq.connect_timeout = time;
Opis: The time in seconds to wait for a backend connection.

Dokumentacja Varnish: first_byte_timeout (2.1) | first_byte_timeout (3.0) | first_byte_timeout (4.1) | first_byte_timeout (5.0)
Składnia: .bereq.first_byte_timeout = time;
Opis: The time in seconds to wait for the first byte from the backend. Not available in pipe mode.

Dokumentacja Varnish: between_bytes_timeout(2.1) | between_bytes_timeout(3.0) | between_bytes_timeout(4.1) | between_bytes_timeout(5.0)
Składnia: .bereq.between_bytes_timeout = time;
Opis: The time in seconds to wait between each received byte from the backend. Not available in pipe mode.

EXAMPLES
backend name {
    .host = 127.0.0.1;
    .port = 8080;
    .connect_timeout = 30;
    .first_byte_timeout = 5;
    .between_bytes_timeout = 5;
    .probe {
        .url = "/";
        .timeout = 1s;
        .window = 8;
        .threshold = 3;
        .initial = 3;
        .interval = 5s;
    }
}



#top vhosts default


Zobacz także vhosts default dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Brak obsługi virtualnych hostów!!! Varnish jest serwerem Proxy/Cache.

Dokumentacja Varnish: syntax (2.1), syntax (3.0), syntax (4.1), syntax (5.0)

EXAMPLES
sub vcl_recv {
  if (req.http.host ~ "^(www.)?example.com$") {
    set req.http.host = "www.example.com";
    set req.backend = www;
  } elsif (req.http.host ~ "^images.example.com$") {
    set req.backend = images;
  } else {
    error 404 "Unknown virtual host";
  }
}



#top vhosts SSL


Zobacz także vhosts SSL dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Brak obsługi virtualnych hostów!!! Varnish jest serwerem Proxy/Cache.

Dokumentacja Varnish: Why no SSL
Dokumentacja Varnish: Why no SSL
Dokumentacja Varnish: Why no SSL



#top ErrorLog


Zobacz także ErrorLog dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Brak obsługi logowania błędów!!! Varnish jest serwerem Proxy/Cache.



#top AccessLog


Zobacz także AccessLog dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: varnishlog (2.1), varnishlog (3.0), varnishlog (4.1), varnishlog (5.0)
Dokumentacja Varnish: varnishncsa (2.1), varnishncsa (3.0), varnishncsa (4.1), varnishncsa (5.0)

Command line arguments:
usage: varnishncsa ... [-a] ... [-w file]
usage: varnishlog ... [-a] ... [-w file]

Manual page in man varnishncsa:
-a
When writing to a file, append to it rather than overwrite it.

-w file
Write log entries to file instead of displaying them. The file will be overwritten unless the -a option was specified.
If varnishncsa receives a SIGHUP while writing to a file, it will reopen the file, allowing the old one to be rotated away.

Manual page in man varnishlog:
-a
When writing to a file, append to it rather than overwrite it.

-w file
Write log entries to file instead of displaying them. The file will be overwritten unless the -a option was specified.
If varnishncsa receives a SIGHUP while writing to a file, it will reopen the file, allowing the old one to be rotated away.

EXAMPLES
Configure variables in file /etc/sysconfig/varnishncsa:
logfile="/var/log/varnish/varnishncsa.log"

Configure variables in file /etc/sysconfig/varnishlog:
logfile="/var/log/varnish/varnishlog.log"



#top LogFormat


Zobacz także LogFormat dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: varnishncsa (2.1), varnishncsa (3.0), varnishncsa (4.1), varnishncsa (5.0)
Command line arguments: (Opcja -F format dostępna jest dopiero od wersji 4.*, we wcześniejszych wersjach varnish nie posiada możliwości konfiguracji formatu logowania.)
usage: varnishncsa ... [-F format]

Manual page in man varnishncsa:
-F format
Set the output log format string.

FORMAT
Specify the log format used. If no format is specified the default log format is used.
The default log format is:
%h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i"

Escape sequences \n and \t are supported.
Supported formatters are:
%b Size of response in bytes, excluding HTTP headers. In CLF format, i.e. a '-' rather than a 0 when no bytes are sent.
%D Time taken to serve the request, in microseconds.
%H The request protocol. Defaults to HTTP/1.0 if not known.
%h Remote host. Defaults to '-' if not known.
%I Total bytes received from client.
%{X}i The contents of request header X.
%l Remote logname (always '-')
%m Request method. Defaults to '-' if not known.
%{X}o The contents of response header X.
%O Total bytes sent to client.
%q The query string, if no query string exists, an empty string.
%r The first line of the request. Synthesized from other fields, so it may not be the request verbatim.
%s Status sent to the client
%t Time when the request was received, in HTTP date/time format.
%{X}t Time when the request was received, in the format specified by X. The time specification format is the same as for strftime(3).
%T Time taken to serve the request, in seconds.
%U The request URL without any query string. Defaults to '-' if not known.
%u Remote user from auth
%{X}x Extended variables. Supported variables are:
Varnish:time_firstbyte Time from when the request processing starts until the first byte is sent to the client.
Varnish:hitmiss Whether the request was a cache hit or miss. Pipe and pass are considered misses.
Varnish:handling How the request was handled, whether it was a cache hit, miss, pass, pipe or error.
VCL_Log:key Output value set by std.log("key:value") in VCL.



#top server status


Zobacz także server status dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: varnishstat (2.1), varnishstat (3.0), varnishstat (4.1), varnishstat (5.0)

EXAMPLES
varnishstat [-1] [-x] [-f field_list] [-l] [-n varnish_name] [-V] [-w delay]

The varnishstat utility displays statistics from a running varnishd(1) instance.

The following options are available:
-1 Instead of presenting of a continuously updated display, print the statistics once and exit.
-f A comma separated list of the fields to display. If it starts with ‘^’ it is used as an exclusion list.
-l Lists the available fields to use with the -f option.
-n Specifies the name of the varnishd instance to get logs from. If -n is not specified, the host name is used.
-V Display the version number and exit.
-w delay Wait delay seconds between updates. The default is 1.
-x Displays the result as XML once.

The columns in the main display are, from left to right:

1. Value
2. Per-second average in the period since last update, or a period if the value can not be averaged
3. Per-second average over process lifetime, or a period if the value can not be averaged
4. Descriptive text

When using the -1 option, the columns in the output are, from left to right:

1. Symbolic entry name
2. Value
3. Per-second average over process lifetime, or a period if the value can not be averaged
4. Descriptive text

When using the -x option, the output is:

<stat>
<name>FIELD NAME</name>
<value>FIELD VALUE</value>
<description>FIELD DESCRIPTION</description>
</stat>

Przykładowa komendy do wyświetlania statystyk w formacie tekstowym:
varnishstat -n /srv/varnish/default -1

Wynik wywołania komendy wyświetlania statystyk:
client_conn                56         0.06 Client connections accepted
client_drop                 0         0.00 Connection dropped, no sess/wrk
client_req                 56         0.06 Client requests received
cache_hit                  17         0.02 Cache hits
cache_hitpass              10         0.01 Cache hits for pass
cache_miss                 29         0.03 Cache misses
backend_conn               39         0.04 Backend conn. success
backend_unhealthy            0         0.00 Backend conn. not attempted
backend_busy                0         0.00 Backend conn. too many
backend_fail                0         0.00 Backend conn. failures
backend_reuse               0         0.00 Backend conn. reuses
backend_toolate             0         0.00 Backend conn. was closed
backend_recycle             0         0.00 Backend conn. recycles
backend_unused              0         0.00 Backend conn. unused
fetch_head                  0         0.00 Fetch head
fetch_length               39         0.04 Fetch with Length
fetch_chunked               0         0.00 Fetch chunked
fetch_eof                   0         0.00 Fetch EOF
fetch_bad                   0         0.00 Fetch had bad headers
fetch_close                 0         0.00 Fetch wanted close
fetch_oldhttp               0         0.00 Fetch pre HTTP/1.1 closed
fetch_zero                  0         0.00 Fetch zero len
fetch_failed                0         0.00 Fetch failed
n_sess_mem                 11          .   N struct sess_mem
n_sess                      0          .   N struct sess
n_object                    1          .   N struct object
n_vampireobject             0          .   N unresurrected objects
n_objectcore                3          .   N struct objectcore
n_objecthead               11          .   N struct objecthead
n_smf                       6          .   N struct smf
n_smf_frag                  2          .   N small free smf
n_smf_large                 2          .   N large free smf
n_vbe_conn                  0          .   N struct vbe_conn
n_wrk                       2          .   N worker threads
n_wrk_create                2         0.00 N worker threads created
n_wrk_failed                0         0.00 N worker threads not created
n_wrk_max               11020        10.85 N worker threads limited
n_wrk_queue                 0         0.00 N queued work requests
n_wrk_overflow              0         0.00 N overflowed work requests
n_wrk_drop                  0         0.00 N dropped work requests
n_backend                   1          .   N backends
n_expired                  28          .   N expired objects
n_lru_nuked                 0          .   N LRU nuked objects
n_lru_saved                 0          .   N LRU saved objects
n_lru_moved                17          .   N LRU moved objects
n_deathrow                  0          .   N objects on deathrow
losthdr                     0         0.00 HTTP header overflows
n_objsendfile               0         0.00 Objects sent with sendfile
n_objwrite                 56         0.06 Objects sent with write
n_objoverflow               0         0.00 Objects overflowing workspace
s_sess                     56         0.06 Total Sessions
s_req                      56         0.06 Total Requests
s_pipe                      0         0.00 Total pipe
s_pass                     10         0.01 Total pass
s_fetch                    39         0.04 Total fetch
s_hdrbytes              21346        21.01 Total header bytes
s_bodybytes            259617       255.53 Total body bytes
sess_closed                56         0.06 Session Closed
sess_pipeline               0         0.00 Session Pipeline
sess_readahead              0         0.00 Session Read Ahead
sess_linger                 0         0.00 Session Linger
sess_herd                   0         0.00 Session herd
shm_records              4320         4.25 SHM records
shm_writes               1014         1.00 SHM writes
shm_flushes                 0         0.00 SHM flushes due to overflow
shm_cont                    0         0.00 SHM MTX contention
shm_cycles                  0         0.00 SHM cycles through buffer
sm_nreq                    68         0.07 allocator requests
sm_nobj                     2          .   outstanding allocations
sm_balloc               12288          .   bytes allocated
sm_bfree           1073729536          .   bytes free
sma_nreq                    0         0.00 SMA allocator requests
sma_nobj                    0          .   SMA outstanding allocations
sma_nbytes                  0          .   SMA outstanding bytes
sma_balloc                  0          .   SMA bytes allocated
sma_bfree                   0          .   SMA bytes free
sms_nreq                    0         0.00 SMS allocator requests
sms_nobj                    0          .   SMS outstanding allocations
sms_nbytes                  0          .   SMS outstanding bytes
sms_balloc                  0          .   SMS bytes allocated
sms_bfree                   0          .   SMS bytes freed
backend_req                39         0.04 Backend requests made
n_vcl                       1         0.00 N vcl total
n_vcl_avail                 1         0.00 N vcl available
n_vcl_discard               0         0.00 N vcl discarded
n_purge                     1          .   N total active purges
n_purge_add                 1         0.00 N new purges added
n_purge_retire              0         0.00 N old purges deleted
n_purge_obj_test            0         0.00 N objects tested
n_purge_re_test             0         0.00 N regexps tested against
n_purge_dups                0         0.00 N duplicate purges removed
hcb_nolock                 56         0.06 HCB Lookups without lock
hcb_lock                   29         0.03 HCB Lookups with lock
hcb_insert                 29         0.03 HCB Inserts
esi_parse                   0         0.00 Objects ESI parsed (unlock)
esi_errors                  0         0.00 ESI parse errors (unlock)
accept_fail                 0         0.00 Accept failures
client_drop_late            0         0.00 Connection dropped late
uptime                   1016         1.00 Client uptime
backend_retry               0         0.00 Backend conn. retry
dir_dns_lookups             0         0.00 DNS director lookups
dir_dns_failed              0         0.00 DNS director failed lookups
dir_dns_hit                 0         0.00 DNS director cached lookups hit
dir_dns_cache_full            0         0.00 DNS director full dnscache
fetch_1xx                   0         0.00 Fetch no body (1xx)
fetch_204                   0         0.00 Fetch no body (204)
fetch_304                   0         0.00 Fetch no body (304)

Przykładowa komendy do wyświetlania statystyk w formacie XML:
varnishstat -n /srv/varnish/default -x

Wynik wywołania komendy wyświetlania statystyk:
<?xml version="1.0"?>
<varnishstat timestamp="2016-04-05T20:29:53">
	<stat>
		<name>client_conn</name>
		<value>56</value>
		<description>Client connections accepted</description>
	</stat>
	<stat>
		<name>client_drop</name>
		<value>0</value>
		<description>Connection dropped, no sess/wrk</description>
	</stat>
	<stat>
		<name>client_req</name>
		<value>56</value>
		<description>Client requests received</description>
	</stat>
	<stat>
		<name>cache_hit</name>
		<value>17</value>
		<description>Cache hits</description>
	</stat>
	<stat>
		<name>cache_hitpass</name>
		<value>10</value>
		<description>Cache hits for pass</description>
	</stat>
	<stat>
		<name>cache_miss</name>
		<value>29</value>
		<description>Cache misses</description>
	</stat>
	<stat>
		<name>backend_conn</name>
		<value>39</value>
		<description>Backend conn. success</description>
	</stat>
	<stat>
		<name>backend_unhealthy</name>
		<value>0</value>
		<description>Backend conn. not attempted</description>
	</stat>
	<stat>
		<name>backend_busy</name>
		<value>0</value>
		<description>Backend conn. too many</description>
	</stat>
	<stat>
		<name>backend_fail</name>
		<value>0</value>
		<description>Backend conn. failures</description>
	</stat>
	<stat>
		<name>backend_reuse</name>
		<value>0</value>
		<description>Backend conn. reuses</description>
	</stat>
	<stat>
		<name>backend_toolate</name>
		<value>0</value>
		<description>Backend conn. was closed</description>
	</stat>
	<stat>
		<name>backend_recycle</name>
		<value>0</value>
		<description>Backend conn. recycles</description>
	</stat>
	<stat>
		<name>backend_unused</name>
		<value>0</value>
		<description>Backend conn. unused</description>
	</stat>
	<stat>
		<name>fetch_head</name>
		<value>0</value>
		<description>Fetch head</description>
	</stat>
	<stat>
		<name>fetch_length</name>
		<value>39</value>
		<description>Fetch with Length</description>
	</stat>
	<stat>
		<name>fetch_chunked</name>
		<value>0</value>
		<description>Fetch chunked</description>
	</stat>
	<stat>
		<name>fetch_eof</name>
		<value>0</value>
		<description>Fetch EOF</description>
	</stat>
	<stat>
		<name>fetch_bad</name>
		<value>0</value>
		<description>Fetch had bad headers</description>
	</stat>
	<stat>
		<name>fetch_close</name>
		<value>0</value>
		<description>Fetch wanted close</description>
	</stat>
	<stat>
		<name>fetch_oldhttp</name>
		<value>0</value>
		<description>Fetch pre HTTP/1.1 closed</description>
	</stat>
	<stat>
		<name>fetch_zero</name>
		<value>0</value>
		<description>Fetch zero len</description>
	</stat>
	<stat>
		<name>fetch_failed</name>
		<value>0</value>
		<description>Fetch failed</description>
	</stat>
	<stat>
		<name>n_sess_mem</name>
		<value>11</value>
		<description>N struct sess_mem</description>
	</stat>
	<stat>
		<name>n_sess</name>
		<value>0</value>
		<description>N struct sess</description>
	</stat>
	<stat>
		<name>n_object</name>
		<value>1</value>
		<description>N struct object</description>
	</stat>
	<stat>
		<name>n_vampireobject</name>
		<value>0</value>
		<description>N unresurrected objects</description>
	</stat>
	<stat>
		<name>n_objectcore</name>
		<value>3</value>
		<description>N struct objectcore</description>
	</stat>
	<stat>
		<name>n_objecthead</name>
		<value>11</value>
		<description>N struct objecthead</description>
	</stat>
	<stat>
		<name>n_smf</name>
		<value>6</value>
		<description>N struct smf</description>
	</stat>
	<stat>
		<name>n_smf_frag</name>
		<value>2</value>
		<description>N small free smf</description>
	</stat>
	<stat>
		<name>n_smf_large</name>
		<value>2</value>
		<description>N large free smf</description>
	</stat>
	<stat>
		<name>n_vbe_conn</name>
		<value>0</value>
		<description>N struct vbe_conn</description>
	</stat>
	<stat>
		<name>n_wrk</name>
		<value>2</value>
		<description>N worker threads</description>
	</stat>
	<stat>
		<name>n_wrk_create</name>
		<value>2</value>
		<description>N worker threads created</description>
	</stat>
	<stat>
		<name>n_wrk_failed</name>
		<value>0</value>
		<description>N worker threads not created</description>
	</stat>
	<stat>
		<name>n_wrk_max</name>
		<value>11020</value>
		<description>N worker threads limited</description>
	</stat>
	<stat>
		<name>n_wrk_queue</name>
		<value>0</value>
		<description>N queued work requests</description>
	</stat>
	<stat>
		<name>n_wrk_overflow</name>
		<value>0</value>
		<description>N overflowed work requests</description>
	</stat>
	<stat>
		<name>n_wrk_drop</name>
		<value>0</value>
		<description>N dropped work requests</description>
	</stat>
	<stat>
		<name>n_backend</name>
		<value>1</value>
		<description>N backends</description>
	</stat>
	<stat>
		<name>n_expired</name>
		<value>28</value>
		<description>N expired objects</description>
	</stat>
	<stat>
		<name>n_lru_nuked</name>
		<value>0</value>
		<description>N LRU nuked objects</description>
	</stat>
	<stat>
		<name>n_lru_saved</name>
		<value>0</value>
		<description>N LRU saved objects</description>
	</stat>
	<stat>
		<name>n_lru_moved</name>
		<value>17</value>
		<description>N LRU moved objects</description>
	</stat>
	<stat>
		<name>n_deathrow</name>
		<value>0</value>
		<description>N objects on deathrow</description>
	</stat>
	<stat>
		<name>losthdr</name>
		<value>0</value>
		<description>HTTP header overflows</description>
	</stat>
	<stat>
		<name>n_objsendfile</name>
		<value>0</value>
		<description>Objects sent with sendfile</description>
	</stat>
	<stat>
		<name>n_objwrite</name>
		<value>56</value>
		<description>Objects sent with write</description>
	</stat>
	<stat>
		<name>n_objoverflow</name>
		<value>0</value>
		<description>Objects overflowing workspace</description>
	</stat>
	<stat>
		<name>s_sess</name>
		<value>56</value>
		<description>Total Sessions</description>
	</stat>
	<stat>
		<name>s_req</name>
		<value>56</value>
		<description>Total Requests</description>
	</stat>
	<stat>
		<name>s_pipe</name>
		<value>0</value>
		<description>Total pipe</description>
	</stat>
	<stat>
		<name>s_pass</name>
		<value>10</value>
		<description>Total pass</description>
	</stat>
	<stat>
		<name>s_fetch</name>
		<value>39</value>
		<description>Total fetch</description>
	</stat>
	<stat>
		<name>s_hdrbytes</name>
		<value>21346</value>
		<description>Total header bytes</description>
	</stat>
	<stat>
		<name>s_bodybytes</name>
		<value>259617</value>
		<description>Total body bytes</description>
	</stat>
	<stat>
		<name>sess_closed</name>
		<value>56</value>
		<description>Session Closed</description>
	</stat>
	<stat>
		<name>sess_pipeline</name>
		<value>0</value>
		<description>Session Pipeline</description>
	</stat>
	<stat>
		<name>sess_readahead</name>
		<value>0</value>
		<description>Session Read Ahead</description>
	</stat>
	<stat>
		<name>sess_linger</name>
		<value>0</value>
		<description>Session Linger</description>
	</stat>
	<stat>
		<name>sess_herd</name>
		<value>0</value>
		<description>Session herd</description>
	</stat>
	<stat>
		<name>shm_records</name>
		<value>4320</value>
		<description>SHM records</description>
	</stat>
	<stat>
		<name>shm_writes</name>
		<value>1014</value>
		<description>SHM writes</description>
	</stat>
	<stat>
		<name>shm_flushes</name>
		<value>0</value>
		<description>SHM flushes due to overflow</description>
	</stat>
	<stat>
		<name>shm_cont</name>
		<value>0</value>
		<description>SHM MTX contention</description>
	</stat>
	<stat>
		<name>shm_cycles</name>
		<value>0</value>
		<description>SHM cycles through buffer</description>
	</stat>
	<stat>
		<name>sm_nreq</name>
		<value>68</value>
		<description>allocator requests</description>
	</stat>
	<stat>
		<name>sm_nobj</name>
		<value>2</value>
		<description>outstanding allocations</description>
	</stat>
	<stat>
		<name>sm_balloc</name>
		<value>12288</value>
		<description>bytes allocated</description>
	</stat>
	<stat>
		<name>sm_bfree</name>
		<value>1073729536</value>
		<description>bytes free</description>
	</stat>
	<stat>
		<name>sma_nreq</name>
		<value>0</value>
		<description>SMA allocator requests</description>
	</stat>
	<stat>
		<name>sma_nobj</name>
		<value>0</value>
		<description>SMA outstanding allocations</description>
	</stat>
	<stat>
		<name>sma_nbytes</name>
		<value>0</value>
		<description>SMA outstanding bytes</description>
	</stat>
	<stat>
		<name>sma_balloc</name>
		<value>0</value>
		<description>SMA bytes allocated</description>
	</stat>
	<stat>
		<name>sma_bfree</name>
		<value>0</value>
		<description>SMA bytes free</description>
	</stat>
	<stat>
		<name>sms_nreq</name>
		<value>0</value>
		<description>SMS allocator requests</description>
	</stat>
	<stat>
		<name>sms_nobj</name>
		<value>0</value>
		<description>SMS outstanding allocations</description>
	</stat>
	<stat>
		<name>sms_nbytes</name>
		<value>0</value>
		<description>SMS outstanding bytes</description>
	</stat>
	<stat>
		<name>sms_balloc</name>
		<value>0</value>
		<description>SMS bytes allocated</description>
	</stat>
	<stat>
		<name>sms_bfree</name>
		<value>0</value>
		<description>SMS bytes freed</description>
	</stat>
	<stat>
		<name>backend_req</name>
		<value>39</value>
		<description>Backend requests made</description>
	</stat>
	<stat>
		<name>n_vcl</name>
		<value>1</value>
		<description>N vcl total</description>
	</stat>
	<stat>
		<name>n_vcl_avail</name>
		<value>1</value>
		<description>N vcl available</description>
	</stat>
	<stat>
		<name>n_vcl_discard</name>
		<value>0</value>
		<description>N vcl discarded</description>
	</stat>
	<stat>
		<name>n_purge</name>
		<value>1</value>
		<description>N total active purges</description>
	</stat>
	<stat>
		<name>n_purge_add</name>
		<value>1</value>
		<description>N new purges added</description>
	</stat>
	<stat>
		<name>n_purge_retire</name>
		<value>0</value>
		<description>N old purges deleted</description>
	</stat>
	<stat>
		<name>n_purge_obj_test</name>
		<value>0</value>
		<description>N objects tested</description>
	</stat>
	<stat>
		<name>n_purge_re_test</name>
		<value>0</value>
		<description>N regexps tested against</description>
	</stat>
	<stat>
		<name>n_purge_dups</name>
		<value>0</value>
		<description>N duplicate purges removed</description>
	</stat>
	<stat>
		<name>hcb_nolock</name>
		<value>56</value>
		<description>HCB Lookups without lock</description>
	</stat>
	<stat>
		<name>hcb_lock</name>
		<value>29</value>
		<description>HCB Lookups with lock</description>
	</stat>
	<stat>
		<name>hcb_insert</name>
		<value>29</value>
		<description>HCB Inserts</description>
	</stat>
	<stat>
		<name>esi_parse</name>
		<value>0</value>
		<description>Objects ESI parsed (unlock)</description>
	</stat>
	<stat>
		<name>esi_errors</name>
		<value>0</value>
		<description>ESI parse errors (unlock)</description>
	</stat>
	<stat>
		<name>accept_fail</name>
		<value>0</value>
		<description>Accept failures</description>
	</stat>
	<stat>
		<name>client_drop_late</name>
		<value>0</value>
		<description>Connection dropped late</description>
	</stat>
	<stat>
		<name>uptime</name>
		<value>1016</value>
		<description>Client uptime</description>
	</stat>
	<stat>
		<name>backend_retry</name>
		<value>0</value>
		<description>Backend conn. retry</description>
	</stat>
	<stat>
		<name>dir_dns_lookups</name>
		<value>0</value>
		<description>DNS director lookups</description>
	</stat>
	<stat>
		<name>dir_dns_failed</name>
		<value>0</value>
		<description>DNS director failed lookups</description>
	</stat>
	<stat>
		<name>dir_dns_hit</name>
		<value>0</value>
		<description>DNS director cached lookups hit</description>
	</stat>
	<stat>
		<name>dir_dns_cache_full</name>
		<value>0</value>
		<description>DNS director full dnscache</description>
	</stat>
	<stat>
		<name>fetch_1xx</name>
		<value>0</value>
		<description>Fetch no body (1xx)</description>
	</stat>
	<stat>
		<name>fetch_204</name>
		<value>0</value>
		<description>Fetch no body (204)</description>
	</stat>
	<stat>
		<name>fetch_304</name>
		<value>0</value>
		<description>Fetch no body (304)</description>
	</stat>
</varnishstat>



#top Modules


Zobacz także Modules dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish:

Budowa monolityczna. Brak obsługi funkcjonalności ładowania modułów (brak modułów)!!!



#top mod-logging


Zobacz także mod-logging dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish:

Budowa monolityczna. Brak obsługi funkcjonalności ładowania modułów (brak modułów)!!!



#top mod-misc


Zobacz także mod-misc dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish:

Budowa monolityczna. Brak obsługi funkcjonalności ładowania modułów (brak modułów)!!!



#top mod-auth


Zobacz także mod-auth dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish:

Budowa monolityczna. Brak obsługi funkcjonalności ładowania modułów (brak modułów)!!!



#top mod-headers


Zobacz także mod-headers dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish:

Budowa monolityczna. Brak obsługi funkcjonalności ładowania modułów (brak modułów)!!!



#top mod-proxy


Zobacz także mod-proxy dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish:

Budowa monolityczna. Brak obsługi funkcjonalności ładowania modułów (brak modułów)!!!
Brak modułu proxy. Varnish jest serwerem Proxy/Cache.
Zobacz przykłady dla vhost default oraz vhosts SSL



#top Access Restrictions


#top AccessAllow


Zobacz także AccessAllow dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: acls (2.1), acls (3.0), acls (4.1), acls (5.0)
Dokumentacja Varnish: subroutines (2.1), subroutines (3.0), subroutines (4.1), subroutines (5.0)

EXAMPLES
acl admin_network {
  "localhost";         // myself
  "192.0.2.0"/24;      // and everyone on the local network
  ! "192.0.2.23";      // except for the dialin router
}

sub vcl_recv {
  if (client.ip ~ admin_network) {
    if (req.http.Cache-Control ~ "no-cache") {
      purge_url(req.url);
    }
  }
}



#top AccessDeny


Zobacz także AccessDeny dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: acls (2.1), acls (3.0), acls (4.1), acls (5.0)
Dokumentacja Varnish: subroutines (2.1), subroutines (3.0), subroutines (4.1), subroutines (5.0)

EXAMPLES
acl forbidden {
  "192.168.168.0"/24;
  "10.10.10.0"/24;
}

sub vcl_recv {
  # Block access from these hosts
  if (client.ip ~ forbidden) {
    error 403 "Forbidden";
  }
  # Block Access from these user agents
  if (req.http.User-Agent ~ "Wget" {
    error 403 "Forbidden";
  }
  return (lookup);
}



#top headers


#top HTTP Header Add


Zobacz także HTTP Header Add dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: set (2.1), set (3.0), set (4.1), set (5.0)
Składnia: set
Opis:

EXAMPLES
set req.http.Accept-Encoding = "gzip";
set obj.http.X-Varnish-IP = server.ip;



#top HTTP Header Set


Zobacz także HTTP Header Set dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: set (2.1), set (3.0), set (4.1), set (5.0)
Składnia: set
Opis:

EXAMPLES
set req.http.Accept-Encoding = "gzip";
set obj.http.X-Varnish-IP = server.ip;



#top HTTP Header Remove


Zobacz także HTTP Header Remove dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: remove (2.1), remove (3.0), remove (4.1), remove (5.0)
Składnia: remove
Składnia: unset
Opis:

EXAMPLES
unset req.http.Cookie;
unset resp.http.X-Varnish;
unset resp.http.Via;
unset resp.http.Age;



#top Header Access


Zobacz także Header Access dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Brak obsługi kontrolowania nagłówków!!!



#top Header MIME


Zobacz także Header MIME dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: mime (2.1), mime (3.0), mime (4.1), mime (5.0)
Składnia: set
Opis:

EXAMPLES




#top TLS Engine


#top TLS Enable


Zobacz także TLS Enable dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Why no SSL



#top TLS Cert/Key File


Zobacz także TLS Cert/Key File dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Why no SSL



#top TLS Protocols


Zobacz także TLS Protocols dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Why no SSL



#top TLS CipherSuite


Zobacz także TLS CipherSuite dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Why no SSL



#top TLS Compression


Zobacz także TLS Compression dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Why no SSL



#top TLS Options


Zobacz także TLS Options dla: Apache | Nginx | Lighttpd | thttpd | HAProxy | Varnish | SQUID

Dokumentacja Varnish: Why no SSL












































Zmodyfikowany ostatnio: 2018/01/04 19:49:27 (6 lat temu), textsize: 54,0 kB, htmlsize: 80,3 kB

Zapraszam do komentowania, zgłaszania sugestii, propozycji, własnych przykładów, ...
Dodaj komentarzKomentarze użytkowników