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
I've been using Nginx for about a decade, and beyond using Varnish every now and then I haven't really had the need to use anything else. Well, recently I started trying out Caddy – in fact, this site is served using Caddy. Would you consider trying Caddy or just stick…
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…
This summer we decided to do a little experiment. Drive through Europe with our Model X while towing a caravan. This journey took us through Norway, Sweden, Denmark, Germany, Austria and back again for a total distance of more than 6.000 km (3700+ miles). https://www.youtube.com/watch?v=88nsPpSoxqU On this trip we got…