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
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…
The essence of smart home/gardening technology is to simplify your life, not complicate it. With the recent arrival of robot mowers that don't require a border wire, I finally felt ready to embrace this technology. The Ecovacs Goat G1 robot mower, with its clean and sleek design, seemed like a…
If you work with WordPress professionally, you almost certainly have a staging environment. Most hosting setups include one, most agencies set one up as a matter of routine. But here is the thing: a lot of the sites people call production are, in practice, staging environments. They just do not…
