Ensighten continues to evaluate HTTP/2 protocol, we do not support it at this time for two main reasons:
- Unnecessary Overhead. Encryption is not required by the HTTP/2 protocol and most modern browsers only support it with SSL. Supporting HTTP/2 today would increase overhead – from key exchange and termination of encryption – to all our unencrypted web tag delivery traffic.
- Mitigate risk to our user interface. Our front-end systems do not support the full HTTP/2 RFC. By not providing support we will avoid the known stability issues between HTTP/2 and the Web Application Firewall (WAF/IPS) system that we use.
Ensighten will continue to evaluate and apply appropriate patches as they become available. Once the risk is eliminated, we will be in a better position to support and enable HTTP/2 on our Manage UI – and others – and the HTTPS traffic on our Tag Delivery Network.