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
A few years ago, I invested in the Satechi 108W PRO USB-C PD Desktop Charger, which served its purpose well for quite some time. However, as the device collection in our home expanded and my need for organization grew, I decided to give the Satechi Dock5 a try. The Satechi…
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…
