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
In today's work-from-home era, a seamless and professional video meeting setup has become an essential part of our daily routine. As remote work becomes more prevalent, it's a good idea to create a space that not only delivers excellent video quality but also integrates smart lighting and automation to create…
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…
As an outdoor enthusiast, there's nothing quite like the feeling of being nestled in a hammock or tucked away in a tent, enjoying the serenity and peace of nature. But as the sun sets and darkness envelops the landscape, a little extra illumination can make all the difference. Enter the…
