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
It's now been well over a year since I started this habit. As a matter of fact, during this time I have replaced the warm showers all together. Update: It's actually been two years now! This was the second time I wanted to experiment with this habit, but the last…
A couple of weeks ago I looked into creating a generator that would output the php-code needed to embed javascript libraries hosted by cdnjs.com. As a part of doing this, I needed to create a searchable table that would filter rows as I typed. Since this table would hold a…
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…
