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:

	sub vcl_hash {
	# … Other vcl_hash stuff
	# If this is a HTTPS request, keep it in a different cache
	if (req.http.X-Forwarded-Proto) {
	hash_data(req.http.X-Forwarded-Proto);
	}

view raw varnish-https-cache.vcl hosted with by GitHub

Here are some other posts you may like

Why I Use a Single 1440p Monitor: A Web Developer’s Perspective on Reducing Distractions

As a web developer, I'm constantly surrounded by technology, code, and designs. In the past, I've experimented with various monitor setups, ranging from dual 27-inch screens to as many as four monitors. While these configurations may have served a purpose at the time, I've come to realize that less is…

Tibber – the Electric power company for the future

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…

Restrict SFTP users to home folder

Here is a guide for setting up SFTP users who's access is restricted to their home directory. Add the following to the end of the /etc/ssh/sshd_config file: Subsystem sftp internal-sftp # This section must be placed at the very end of sshd_config Match Group sftponly ChrootDirectory %h ForceCommand internal-sftp AllowTcpForwarding…