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
Advanced Custom Fields is used a lot by WordPress developers, and it comes with a lot of handy fields. It's also very developer friendly, for example giving the ability to populate a select field through filters. But in some cases you may have a crazy amount of options/choices to populate…
Load balancers are incredibly useful when a single server isn't capable of handling the load or if you wan't greater reliability. But what if bandwidth is the limiting factor, what do you do then? And what tools from the Digital Ocean toolbox can you use? In a recent project I…
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…