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
Smart home technology should always enhance your home and never complicate it. That's why I believe in having wall switches for essential functions, even if they're also controlled by motion sensors or other means. One of the newer option in this segment is the Tap Dial, and I'm excited to…
It's been about a month since I sold our Tesla Model S 70D, as our Model X 90D 6-seater was about to arrive. Now that I am used to the Model X, I thought I might do a write up comparing the two. Both cars are absolutely great though – more…
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…