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…
Earlier this year Digital Ocean launched Managed Databases. At that time, only PostgreSQL was made available, and now MySQL and Redis have finally landed as well. I have now done some experimenting with this service, and here are my first impressions. In short; Digital Ocean's Managed Databases allow you set…
This is hands down the question I'm asked most often, "How does the Tesla Model S handle the norwegian winters?" The short answer is great! Naturally opinions will vary, but for me it has been awesome. It has made me leave my petrol car out in the cold, literally. Preheated Lets…
