<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I think the choice between HaProxy and Hitch is probably one where
you have to look at what you need or might need in the future and
what you already know.<br>
My decision to use HaProxy was based on several criteria:<br>
- We already use HaProxy at other locations so I was familiar with
the product and it's configuration.<br>
- Using Hitch would mean that I would need to maintain another part
of software.<br>
- I wanted to be able to make traffic routing decisions before the
request hits Varnish. Send requests to different backend etc.<br>
- I wanted to do some rewrites before the traffic hits Varnish.<br>
<br>
Based on those criteria I decided to put HaProxy in front of
Varnish. Your criteria will very likely be different.<br>
<br>
Jan Hugo Prins<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/16/2017 08:56 AM, Admin
Beckspaced wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5a696be0-c0a7-5317-a270-db1e7d1031c5@beckspaced.com">Thanks
a lot for your suggestion for using HaProxy ;)
<br>
<br>
My thinking was just: why install another bit of software when
apache is able to do the SSL termination.
<br>
But like Andrei said, if traffic spikes hit the apache runaround
will not be the optimal solution.
<br>
<br>
Do you guys have any recent up-to-date tutorials / howtos on
setting up HaProxy as SSL terminator in front of varnish.
<br>
also doing the SSL redirects ...
<br>
<br>
Did look around for Hitch but wasn't very pleased with the info
provided ;(
<br>
<br>
Any hints are welcome & thanks for your help & replies ;)
<br>
<br>
Greetings
<br>
Becki
<br>
<br>
<br>
<br>
On 15.08.2017 22:04, Jan Hugo Prins | BetterBe wrote:
<br>
<blockquote type="cite">I would not do it like that.
<br>
Better is to use something like Hitch or HaProxy (my preference)
and put that in front of Varnish.
<br>
Then HaProxy / Hitch can terminate all SSL traffic, and HaProxy
can also do your redirect to SSL if needed.
<br>
Then in Varnish you use the Apache server as a backend and let
it only serve what it needs to serve.
<br>
Use the ProxyProtocol to send the client information from
HaProxy to Vernish.
<br>
In Varnish you need to put the client IP into the
X-Forwarded-For header.
<br>
In Apache you can then use this header to have the real client
IP address.
<br>
<br>
This way you have the real client IP information on all layers.
<br>
<br>
Jan Hugo Prins
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<table
style="font-family:Arial,Roboto;font-size:12px;line-height:1.38em;border-collapse:collapse;color:#332F60;letter-spacing:0.1px;white-space:nowrap;">
<colgroup><col style="width:174px"><col style="width:174px"><col
style="width:166px"></colgroup> <tbody>
<tr>
<td colspan="3"
style="font-size:13px;color:#000;line-height:20px;padding:0
0 42px 0"> Kind regards<br>
<br>
Jan Hugo Prins<br>
<i>DevOps Engineer</i> </td>
</tr>
<tr>
<td colspan="3" style="padding:0 0 42px 0"><a
href="https://betterbe.com"><img
src="cid:part1.BE8351F0.2E4F2DAE@betterbe.com"
style="width:376px"></a></td>
</tr>
<tr>
<td>
Auke Vleerstraat 140 E<br>
7547 AN Enschede<br>
CC no. <a
href="https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=080975270000"
style="text-decoration:none;color:#332F60;">08097527</a>
</td>
<td>
<b>T</b> <a href="tel:+31534800694"
style="text-decoration:none;color:#332F60;">+31 (0) 53
48 00 694</a><br>
<b>E</b> <a href="mailto:jprins@betterbe.com"
style="text-decoration:none;color:#332F60;">jprins@betterbe.com</a><br>
<b>M</b> <a href="tel:+31%20%280%296%20263%2058%20951"
style="text-decoration:none;color:#332F60;">+31 (0)6 263
58 951</a>
</td>
<td style="vertical-align:bottom"><a
href="https://www.betterbe.com"
style="color:#E73C57;font-weight:bold;text-decoration:none;">www.betterbe.com</a></td>
</tr>
<tr>
<td colspan="3" style="font-size:
9px;color:#A0A6B2;letter-spacing:0;line-height:1.5em;padding-top:42px;">
BetterBe accepts no liability for the content of this
email, or for the consequences of any actions taken on the
basis<br>
of the information provided, unless that information is
subsequently confirmed in writing. If you are not the
intended<br>
recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the
contents of this<br>
information is strictly prohibited.
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>