A high traffic site I host for a client needed to be available on both HTTP and HTTPS. This particular site, though, needed different caches depending on what scheme was used.
Note: Since Varnish doesn’t support HTTPS, it is in this case placed behind Nginx. Nginx then indicates any HTTPS requests passed onto by setting the X-Forwarded-Proto
header.
With Varnish handling caching, this is what needed to be added to the configuration:
Here are some other posts you may like
Remember when the EU nearly ditched daylight savings before the pandemic paused everything? As a parent, I know how tough the time change can be on kids. This year, I tried something new based on Matthew Walker's 'Why We Sleep'. We gradually shifted our bedtimes and wake-up times by 15…
I recently bought a hammock, and thought that I'd try going hammock camping. So I packed my backpack and headed into the woods. Here are some of my thoughts after having spent the night outside in below freezing temperatures with a hammock. Setting up Setting up the campsite was just…
Electric power companies, in general, are pretty much the same. Tibber however, is unlike any electricity company I had seen before. They try to utilise the data we get from smart devices, which they also sell, to save electricity, money and the environment, as well as improving comfort. It’s a…