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
Plenty of people today still have their reservation about buying an electric car. So, after having driven exclusively electric for the last two years, why is it that I think Teslas are awesome and wouldn't even consider going back? 1. It's a computer on wheels I came from a new…
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…
When I first started to develop WordPress sites, I came across an issue. I had never used WordPress like my customers did. Developers and users usually don't see things the same way. Besides, most of them had their experiences from one of the default themes. I quickly understood that I…