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
There is a question that a lot of Tesla owners are asking these days, is Autopilot 2.0 as good as 1.0 yet? At this point the two generations are pretty much equal as far as Autosteer goes – even though some other features are still lacking. Look below for what…
Let's get straight to the point, I'm terrible at breakfast. It's always been way to easy for me to just skip it and not eat anything until lunch. Not exactly ideal. Since I'm not the least motivated to make breakfast in the morning, I decided to go for something 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…
