Approved by the Internet Engineering Task Force (IETF), HTTP/2 is the first major update to HTTP since 1999, when HTTP/1.1 was standardized. Designed with performance in mind, one of the biggest goals of HTTP/2 implementation is to decrease latency while maintaining a high-level compatibility with HTTP/1.1
It reduces latency by enabling full request and response multiplexing, minimize protocol overhead via efficient compression of HTTP header fields, and add support for request prioritization and server push.
HTTP/2 enabled servers fallback to HTTP/1.1 when the client cannot handle the new protocol. So, it’s important to test the same server for both HTTP/1.1 and HTTP/2 clients.
NeoLoad recorder can either record HTTP/1.1 or HTTP/2 traffic from the server. In terms of playing back, NeoLoad makes it easy to mix HTTP/1.1 and HTTP/2 for the same User Path by customizing the agent settings used to play the traffic. Only one design required for the two protocols.
In order to increase the visibility on HTTP/2 testing, NeoLoad reports shows for each server if the server is HTTP/2 compatible and if HTTP/2 has been used during the test