Let me describe a failure that only affected Safari users on macOS. Not Chrome. Not Firefox. Not Windows. Just Safari on Mac. For 4 days.
My British IPTV service was working for most customers. But Safari on Mac users couldn't connect. Same error. Same symptoms. Same frustration. My IPTV Reseller Panel logs showed no errors. The streams were online. Safari users were locked out.
Here's the thing — HTTP/3 is a new protocol. Safari supports it. My CDN had a bug in their HTTP/3 implementation. Safari users were being served HTTP/3 connections that failed. Chrome and Firefox fell back to HTTP/2. Safari didn't. Safari users were blocked.
In most cases, resellers don't understand HTTP/3. They blame Safari. They blame Apple. The problem is protocol negotiation. Your British IPTV business needs to support HTTP/3 properly. Not optional. Essential.
What actually works is testing your service on every browser and every protocol. HTTP/2. HTTP/3. QUIC. Every combination.
One real-world scenario: a reseller in Manchester tested his service on Safari with HTTP/3. It failed. He disabled HTTP/3 on his CDN. Safari users could connect. His customers never knew.
The pattern that keeps showing up is that new protocols bring new failures. Your British IPTV business needs protocol testing. Not just HTTP/2. HTTP/3. QUIC. Everything.
The midnight HTTP/3 failure taught me to test every protocol. Not just the old ones. The new ones too.
A loose sentence: Safari users deserve to watch too. Test your protocols. Don't leave Apple users behind.