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
I wanted to monitor the power usage of our water heater. However, because it draws 3000W, there weren't a ton of options for what smart plug to use that supported both the needed wattage, zigbee and power monitoring. I ended up buying an ELKO SmartPlug 16A Zigbee plug. Since there…
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…
Here is a quick guide for downloading WordPress from the command line. In this case, I would be logged inn via SSH on my server, and ready to set up the site mydomain.com. The root folder for that domain will be at /var/www/mydomain.com/www/. Let's start by navigating to /var/www/mydomain.com cd…
