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
Ever since we decided to get a heat pump in our house, I had my mind set on getting a Sensibo Sky. This is a device that makes your heat pump or AC smart and adds control via your smart phone. So, shortly after having the heat pump installed, we…
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…
When I need to debug a WordPress quickly, I usually reach for this quick command: wp plugin install query-monitor --activate wp config set WP_DEBUG true --raw wp config set WP_DEBUG_LOG true --raw wp config set WP_DEBUG_DISPLAY false --raw wp config set SAVEQUERIES true --raw Let's take a quick look at…
