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
This is a question I have heard (too) many time. How does one reset the root MySQL password on Ubuntu. In order to make this as simple as possible I created a shell script (you can see it below) that does just that. What does it do? I'm glad you…
Arc is a new player in the browser field, crafted by the New York-based Browser Company. The company positions Arc as a tool that makes browsing the Internet more calm, collected, and capable, aiming to replace existing browsers like Chrome and minimize distractions and tab overload]. However, currently, it's not…
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…
