You can now include the HTTP/3 behavior in your API Acceleration property to support secure HTTP/3 connections between a requesting media player and the Akamai edge.
HTTP/3 keeps HTTP/1.1 and HTTP/2 concepts, but it moves away from the conventional transmission control protocol (TCP) transport layer. HTTP/3 uses the IETF QUIC protocol instead. It handles streams by itself which supports improved performance and a faster connection setup.
HTTP/3 support isn't unique to API Acceleration. For details on its use, see the HTTP/3 topic in the Property Manager documentation.