Gecko [ www.finalhopeacademy.com ]

Name	Size	Permission
command-line.html	10.23 KB	-rw-r--r--
compression.html	11.79 KB	-rw-r--r--
devicedetection.html	21.88 KB	-rw-r--r--
esi.html	11.71 KB	-rw-r--r--
increasing-your-hitrate.html	61.46 KB	-rw-r--r--
index.html	11.92 KB	-rw-r--r--
intro.html	10.24 KB	-rw-r--r--
operation-logging.html	9.3 KB	-rw-r--r--
operation-statistics.html	8.39 KB	-rw-r--r--
params.html	5.66 KB	-rw-r--r--
performance.html	10.05 KB	-rw-r--r--
purging.html	13.81 KB	-rw-r--r--
report.html	5.48 KB	-rw-r--r--
run_cli.html	15.13 KB	-rw-r--r--
run_security.html	17.29 KB	-rw-r--r--
running.html	7.21 KB	-rw-r--r--
sizing-your-cache.html	6.17 KB	-rw-r--r--
storage-backends.html	11.52 KB	-rw-r--r--
troubleshooting.html	16.57 KB	-rw-r--r--
vcl-actions.html	6.04 KB	-rw-r--r--
vcl-backends.html	21.2 KB	-rw-r--r--
vcl-built-in-subs.html	31.33 KB	-rw-r--r--
vcl-example-acls.html	5.87 KB	-rw-r--r--
vcl-example-manipulating-heade...	6.33 KB	-rw-r--r--
vcl-example-manipulating-respo...	6.47 KB	-rw-r--r--
vcl-example-websockets.html	6.95 KB	-rw-r--r--
vcl-examples.html	5.68 KB	-rw-r--r--
vcl-grace.html	9.83 KB	-rw-r--r--
vcl-hashing.html	8.52 KB	-rw-r--r--
vcl-inline-c.html	6.14 KB	-rw-r--r--
vcl-separate.html	13.18 KB	-rw-r--r--
vcl-syntax.html	10.49 KB	-rw-r--r--
vcl-variables.html	5.93 KB	-rw-r--r--
vcl.html	7.72 KB	-rw-r--r--

Code Editor : vcl-backends.html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
 <title>Backend servers &#8212; Varnish version 5.2.1 documentation</title>
 
 <link rel="stylesheet" href="../_static/classic.css" type="text/css" />
 <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
 
 <script type="text/javascript">
 var DOCUMENTATION_OPTIONS = {
 URL_ROOT: '../',
 VERSION: '5.2.1',
 COLLAPSE_INDEX: false,
 FILE_SUFFIX: '.html',
 HAS_SOURCE: true
 };
 </script>
 <script type="text/javascript" src="../_static/jquery.js"></script>
 <script type="text/javascript" src="../_static/underscore.js"></script>
 <script type="text/javascript" src="../_static/doctools.js"></script>
 <link rel="index" title="Index" href="../genindex.html" />
 <link rel="search" title="Search" href="../search.html" />
 <link rel="top" title="Varnish version 5.2.1 documentation" href="../index.html" />
 <link rel="up" title="VCL - Varnish Configuration Language" href="vcl.html" />
 <link rel="next" title="Hashing" href="vcl-hashing.html" />
 <link rel="prev" title="actions" href="vcl-actions.html" /> 
 </head>
 <body role="document">
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="vcl-hashing.html" title="Hashing"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="vcl-actions.html" title="actions"
 accesskey="P">previous</a> |</li>
 <li class="nav-item nav-item-0"><a href="../index.html">Varnish version 5.2.1 documentation</a> &#187;</li>
 <li class="nav-item nav-item-1"><a href="index.html" >The Varnish Users Guide</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="vcl.html" accesskey="U">VCL - Varnish Configuration Language</a> &#187;</li> 
 </ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body" role="main">
 
 <div class="section" id="backend-servers">
<h1>Backend servers<a class="headerlink" href="#backend-servers" title="Permalink to this headline">¶</a></h1>
Varnish has a concept of &quot;backend&quot; or &quot;origin&quot; servers. A backend
server is the server providing the content Varnish will accelerate.
Our first task is to tell Varnish where it can find its backends. Start
your favorite text editor and open the relevant VCL file.
Somewhere in the top there will be a section that looks a bit like this.:
<div class="highlight-default"><div class="highlight"><pre># backend default {
# .host = &quot;127.0.0.1&quot;;
# .port = &quot;8080&quot;;
# }
</pre></div>
</div>
We remove the comment markings in this text stanza making the it look like.:
<div class="highlight-default"><div class="highlight"><pre>backend default {
 .host = &quot;127.0.0.1&quot;;
 .port = &quot;8080&quot;;
}
</pre></div>
</div>
Now, this piece of configuration defines a backend in Varnish called
default. When Varnish needs to get content from this backend it will
connect to port 8080 on localhost (127.0.0.1).
Varnish can have several backends defined you can even join
several backends together into clusters of backends for load balancing
purposes.
</div>
<div class="section" id="multiple-backends">
<h1>Multiple backends<a class="headerlink" href="#multiple-backends" title="Permalink to this headline">¶</a></h1>
At some point you might need Varnish to cache content from several
servers. You might want Varnish to map all the URL into one single
host or not. There are lot of options.
Lets say we need to introduce a Java application into out PHP web
site. Lets say our Java application should handle URL beginning with
<cite>/java/</cite>.
We manage to get the thing up and running on port 8000. Now, lets have
a look at the <cite>default.vcl</cite>.:
<div class="highlight-default"><div class="highlight"><pre>backend default {
 .host = &quot;127.0.0.1&quot;;
 .port = &quot;8080&quot;;
}
</pre></div>
</div>
We add a new backend.:
<div class="highlight-default"><div class="highlight"><pre>backend java {
 .host = &quot;127.0.0.1&quot;;
 .port = &quot;8000&quot;;
}
</pre></div>
</div>
Now we need tell Varnish where to send the difference URL. Lets look at <cite>vcl_recv</cite>.:
<div class="highlight-default"><div class="highlight"><pre>sub vcl_recv {
 if (req.url ~ &quot;^/java/&quot;) {
 set req.backend_hint = java;
 } else {
 set req.backend_hint = default;
 }
}
</pre></div>
</div>
It's quite simple, really. Lets stop and think about this for a
moment. As you can see you can define how you choose backends based on
really arbitrary data. You want to send mobile devices to a different
backend? No problem. <code class="docutils literal">if (req.http.User-agent ~ /mobile/) ..</code> should do the
trick.
Without an explicit backend selection, varnish will continue using
the <cite>default</cite> backend. If there is no backend named <cite>default</cite>, the
first backend found in the vcl will be used as the default backend.
</div>
<div class="section" id="backends-and-virtual-hosts-in-varnish">
<h1>Backends and virtual hosts in Varnish<a class="headerlink" href="#backends-and-virtual-hosts-in-varnish" title="Permalink to this headline">¶</a></h1>
Varnish fully supports virtual hosts. They might however work in a somewhat
counter-intuitive fashion since they are never declared
explicitly. You set up the routing of incoming HTTP requests in
<cite>vcl_recv</cite>. If you want this routing to be done on the basis of virtual
hosts you just need to inspect <cite>req.http.host</cite>.
You can have something like this:
<div class="highlight-default"><div class="highlight"><pre>sub vcl_recv {
 if (req.http.host ~ &quot;foo.com&quot;) {
 set req.backend_hint = foo;
 } elsif (req.http.host ~ &quot;bar.com&quot;) {
 set req.backend_hint = bar;
 }
}
</pre></div>
</div>
Note that the first regular expressions will match &quot;foo.com&quot;,
&quot;www.foo.com&quot;, &quot;zoop.foo.com&quot; and any other host ending in &quot;foo.com&quot;. In
this example this is intentional but you might want it to be a bit
more tight, maybe relying on the <code class="docutils literal">==</code> operator in stead, like this:
<div class="highlight-default"><div class="highlight"><pre>sub vcl_recv {
 if (req.http.host == &quot;foo.com&quot; || req.http.host == &quot;www.foo.com&quot;) {
 set req.backend_hint = foo;
 }
}
</pre></div>
</div>
</div>
<div class="section" id="directors">
<h1>Directors<a class="headerlink" href="#directors" title="Permalink to this headline">¶</a></h1>
You can also group several backend into a group of backends. These
groups are called directors. This will give you increased performance
and resilience.
You can define several backends and group them together in a
director. This requires you to load a VMOD, a Varnish module, and then to
call certain actions in <cite>vcl_init</cite>.:
<div class="highlight-default"><div class="highlight"><pre>import directors; # load the directors

backend server1 {
 .host = &quot;192.168.0.10&quot;;
}
backend server2 {
 .host = &quot;192.168.0.10&quot;;
}

sub vcl_init {
 new bar = directors.round_robin();
 bar.add_backend(server1);
 bar.add_backend(server2);
}

sub vcl_recv {
 # send all traffic to the bar director:
 set req.backend_hint = bar.backend();
}
</pre></div>
</div>
This director is a round-robin director. This means the director will
distribute the incoming requests on a round-robin basis. There is
also a random director which distributes requests in a, you guessed it,
random fashion. If that is not enough, you can also write your own director
(see <a class="reference internal" href="../reference/directors.html#ref-writing-a-director">Writing a Director</a>).
But what if one of your servers goes down? Can Varnish direct all the
requests to the healthy server? Sure it can. This is where the Health
Checks come into play.
</div>
<div class="section" id="health-checks">
<h1>Health checks<a class="headerlink" href="#health-checks" title="Permalink to this headline">¶</a></h1>
Lets set up a director with two backends and health checks. First let
us define the backends:
<div class="highlight-default"><div class="highlight"><pre>backend server1 {
 .host = &quot;server1.example.com&quot;;
 .probe = {
 .url = &quot;/&quot;;
 .timeout = 1s;
 .interval = 5s;
 .window = 5;
 .threshold = 3;
 }
}

backend server2 {
 .host = &quot;server2.example.com&quot;;
 .probe = {
 .url = &quot;/&quot;;
 .timeout = 1s;
 .interval = 5s;
 .window = 5;
 .threshold = 3;
 }
}
</pre></div>
</div>
What is new here is the <code class="docutils literal">probe</code>. In this example Varnish will check the
health of each backend every 5 seconds, timing out after 1 second. Each
poll will send a GET request to /. If 3 out of the last 5 polls succeeded
the backend is considered healthy, otherwise it will be marked as sick.
Refer to the <a class="reference internal" href="../reference/vcl.html#reference-vcl-probes">Probes</a> section in the
<a class="reference internal" href="../reference/vcl.html#vcl-7">VCL</a> documentation for more information.
Now we define the 'director':
<div class="highlight-default"><div class="highlight"><pre>import directors;

sub vcl_init {
 new vdir = directors.round_robin();
 vdir.add_backend(server1);
 vdir.add_backend(server2);
}
</pre></div>
</div>
You use this <cite>vdir</cite> director as a backend_hint for requests, just like
you would with a simple backend. Varnish will not send traffic to hosts
that are marked as unhealthy.
Varnish can also serve stale content if all the backends are down. See
<a class="reference internal" href="vcl-grace.html#users-guide-handling-misbehaving-servers">Misbehaving servers</a> for more information on
how to enable this.
Please note that Varnish will keep health probes running for all loaded
VCLs. Varnish will coalesce probes that seem identical - so be careful
not to change the probe config if you do a lot of VCL loading. Unloading
the VCL will discard the probes. For more information on how to do this
please see ref:<cite>reference-vcl-director</cite>.
</div>

</div>
 </div>
 </div>
 <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
 <div class="sphinxsidebarwrapper">
 <h3><a href="../index.html">Table Of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">Backend servers</a></li>
<li><a class="reference internal" href="#multiple-backends">Multiple backends</a></li>
<li><a class="reference internal" href="#backends-and-virtual-hosts-in-varnish">Backends and virtual hosts in Varnish</a></li>
<li><a class="reference internal" href="#directors">Directors</a></li>
<li><a class="reference internal" href="#health-checks">Health checks</a></li>
</ul>

<h4>Previous topic</h4>
 <a href="vcl-actions.html"
 title="previous chapter">actions</a>
 <h4>Next topic</h4>
 <a href="vcl-hashing.html"
 title="next chapter">Hashing</a>
 <div role="note" aria-label="source link">
 <h3>This Page</h3>
 <ul class="this-page-menu">
 <li><a href="../_sources/users-guide/vcl-backends.txt"
 rel="nofollow">Show Source</a></li>
 </ul>
 </div>
<div id="searchbox" style="display: none" role="search">
 <h3>Quick search</h3>
 <form class="search" action="../search.html" method="get">
 <div><input type="text" name="q" /></div>
 <div><input type="submit" value="Go" /></div>
 <input type="hidden" name="check_keywords" value="yes" />
 <input type="hidden" name="area" value="default" />
 </form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
 </div>
 </div>
 <div class="clearer"></div>
 </div>
 <div class="related" role="navigation" aria-label="related navigation">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="vcl-hashing.html" title="Hashing"
 >next</a> |</li>
 <li class="right" >
 <a href="vcl-actions.html" title="actions"
 >previous</a> |</li>
 <li class="nav-item nav-item-0"><a href="../index.html">Varnish version 5.2.1 documentation</a> &#187;</li>
 <li class="nav-item nav-item-1"><a href="index.html" >The Varnish Users Guide</a> &#187;</li>
 <li class="nav-item nav-item-2"><a href="vcl.html" >VCL - Varnish Configuration Language</a> &#187;</li> 
 </ul>
 </div>
 <div class="footer" role="contentinfo">
 &#169; Copyright 2010-2014, Varnish Software AS.
 Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.4.9.
 </div>
 </body>
</html>

${this.title}

Code Editor : vcl-backends.html