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
Hi, and thanks for checking out my site! I'm Thomas, I work as a web developer and live in Norway just outside of Oslo. If you meet me in person you will quickly find me talking about one of 3 things – technology, sustainability and creativity. If I'm getting really…
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…
Tesla is still working hard on it's first mass market car, namely the Tesla Model 3. For a long time though, we have known that Tesla has also planned a Tesla Model Y. This will be a compact SUV, in other words, a smaller Model X. The Model Y will…
