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
As an outdoor enthusiast, there's nothing quite like the feeling of being nestled in a hammock or tucked away in a tent, enjoying the serenity and peace of nature. But as the sun sets and darkness envelops the landscape, a little extra illumination can make all the difference. Enter the…
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…
Recently I was asked about jQuery's resize event. It runs its resize while the users resizes the window – meaning it can be triggered hundreds of times before ending the resize. Is there a way to wait until the user is done resizing? I know jQuery isn't the coolest kid…
