Skip to content

samsung internet: drop http/3 support for all modern versions #7355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

morpig
Copy link

@morpig morpig commented Aug 1, 2025

Samsung Internet is our top 3 browser clients and none of the modern & latest versions serve traffic over HTTP/3.

Based on real-world data, only 0.04% traffic is served over HTTP/3 and those versions are 7.2 - 7.4.

With this PR, we're proposing to disable HTTP/3 support for Samsung Internet from version 8.2 upwards to the current version, unless there is counter data/stats from other parties that suggests otherwise.

Screenshot 2025-08-01 at 23 40 312

We can confirm that this is not a server-side issue and HTTP/3 leads in ChromeMobile UAs.

Screenshot 2025-08-01 at 23 49 55

Samsung Internet UAs that support HTTP/3:

Mozilla/5.0 (Linux; Android 10; SAMSUNG SM-A013G Build/QP1A.190711.020; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 SamsungBrowser/7.4 Chrome/138.0.7204.158 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 11; SAMSUNG SM-A022F Build/RP1A.200720.012; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 SamsungBrowser/7.4 Chrome/138.0.7204.157 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 8.1.0; SAMSUNG SM-A260G Build/OPR6; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 SamsungBrowser/7.2 Chrome/138.0.7204.168 Mobile Safari/537.36

This data is supported from both browserstack + real device testing (Z Flip 6 SM-F741B, Internet app ver 28.0.0.59, One UI 6.1.1, Android 14)

image image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant