Media acceleration works under the covers of video transport with UDP(QUIC) and provides transparent fallback to TCP. As such, it's not always readily apparent which underlying protocol is being utilized at any given time. This transparency is by design and not typically something end-users care about or even notice as long as they are receiving a great user experience !
But sometimes, when first setting up Media Acceleration on a new property or configuration, it is helpful to confirm everything is working as intended. Luckily, the process is very straightforward using the built-in developer tools within Chrome.
Checking if content is accelerated over QUIC:
1. Open Chrome browser and navigate to the webpage containing your Accelerated content.
2. Right-click on the page and choose 'Inspect'
3. The Chrome developer tools window will open and you will look to switch to the 'Network' view
4. Right click on header of the requests table and verify that the Protocol option is checked
5. Reload the page
6. You should start to see accelerated requests issued with http/2+quic/35 listed in the protocol column. Note: quic/35 simply denotes a version and may be different than at the time of writing this guide.
7.When clicking on one of the transactions, you should be able to see the alt-svc header. This can be useful troubleshooting if your segment downloads are showing up as http/1.1 instead of quic.
As always, if you have questions on your specific configuration, please visit the main Media Acceleration community page and 'Ask a Question' !