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…
Panic, the company behind apps such as Coda and Transmit, has released a new app called Status Board. This app is in essence a widget hub for your iPad, showcasing cool stuff such as tweets, e-mail, calendar and much more. One of the most awesome things though is the ability…
In the realm of home automation, Home Assistant stands out for its flexibility and customization capabilities. A common scenario, when working with blueprints, involves using triggers based on input variables. But what if you need to modify these inputs for different triggers? This challenge led me to a solution that…