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
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…
A common issue people experience with Gravity Forms is related to tabbing from one input to another. Especially when multiple forms are displayed on a page. The issue here is that it adds a tabindex attribute to all input elements. Tabindex in Gravity Froms The tabindex attribute tells the browser…
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…
