Seperate Varnish caching for HTTP and HTTPS

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:

Related

How to see if a Tesla has AP

I see people ask about this a lot. How can you know if a car has Autopilot hardware, and if it does, what version? Even then the question remains, has it been enabled? I'll answer all those questions below. For more information about the difference between AP1 and AP2 check…

First impression of Digital Ocean’s Managed Databases

Last night Digital Ocean launched Managed Databases, a service I have been looking forward to. For now it's only available for PostgreSQL (which I hardly ever use) but MySQL support is just around the corner. I've taken a look at what the service offers and here are some of my…

Time-lapse of New York – Sandy visits

https://vimeo.com/52450287 Last night a friend of mine gave me the idea of creating a time-lapse video of New York using the images by the NY-Times webcam. The video shows New York between 15:30 and 08:30 (local time) last night as Sandy hit. I used a simple script to download one…