I would not do it like that.
Better is to use something like Hitch or HaProxy (my preference) and put
that in front of Varnish.
Then HaProxy / Hitch can terminate all SSL traffic, and HaProxy can also
do your redirect to SSL if needed.
Then in Varnish you use the Apache server as a backend and let
Hello there ;)
I'm running varnish in front of my apache on port 80 without any issues
so far.
Recently I decided to also use varnish for SSL connections
To do so I first do a http to https redirect within varnish VCL
if ( req.http.X-Forwarded-Proto !~ "(?i)https" ) {
return (synth(750,
So, if I understood, that's Apache in front of Varnish, not the other way
around. But let's not get lost on semantics
Varnish fanboy version: drop Apache, and use Hitch (http://hitch-tls.org/)
to handle SSL/TLS. That only works if Apache is only there for SSL
termination and not for other tasks
On 08/11/17 12:22 PM, Dridi Boukelmoune wrote:
>> The Wordpress plugin is supposed to clean the whole cache for a website
>> when clicking on a button saying "Clear cache".
>>
>> You say from the varnishlog excerpt I sent that´s not the correct way
>> of doing so, or apparently what is logged by
