
As you might know, the latest Varnish Enterprise release (6.0.6r2) adds support for in-process, or native, TLS. What does this mean, though, and why add this feature, why now?
As you might know, the latest Varnish Enterprise release (6.0.6r2) adds support for in-process, or native, TLS. What does this mean, though, and why add this feature, why now?
Technology has breathed new life into - and in many ways completely changed various industries. While some industries have disappeared, others have expanded, adding to brick-and-mortar empires. iGaming is one such industry, emerging to meet a massive consumer demand for online casino and e-sports betting action. The gaming and betting industry is constantly changing to keep up both with technical innovation and legal and regulatory requirements. A middle ground where performance technology and automated regulatory tools meet is where things stand today.
As you probably know, Varnish has always been a very secure piece of software but so far, that safety only applied to itself and therefore, a malicious request could still go through it and hurt your backend. But as a reverse-proxy (load-balancer, origin shield, etc.), Varnish is going to see everything the backend receives and sends, so there's a great opportunity here to sanitize the traffic before it reaches it.
The Varnish blog is where our team writes about all things related to Varnish Cache and Varnish Software...or simply vents.
0 Comments