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
One of the recent introductions to the already versatile Home Assistant ecosystem is the Condition Selector for blueprints. At its core, this feature seems simple, but its implications for blueprint flexibility are profound. My usecase I've personally used this to update my smart lighting setup. I have one blueprint that…
When Sandy was about to hit New York, @jorgenb came up with a great idea. Download the images from the NY-times webcam and make a timelapse of it. A few minutes later I had a very simple script ready, and could leave my server to the task. The video I…
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…
