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
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…
Soon after the launch of StatusBoard I published a short example of how the app could be used to display server statistics. After a lot of feedback it seems that what was of most interest to readers was what wasn't in the post, the graph that displays historic server load…
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…
