| Summary: | WebKitGTK based browser detected as bot by botguard | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Bartek Sabat <Cloud11665> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | bfulgham, bugs-noreply, mcatanzaro |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=240041 | ||
|
Description
Bartek Sabat
2022-07-23 10:29:04 PDT
Thanks for reporting this. Usually these websites can be fixed by simply adding a user agent quirk. But it's certainly possible you've found the first case that will require something tougher. Quick summary of discussion on Matrix: we think user agent quirks will not work here. We are not sure specifically what they use to decide to discriminate against us. My pet theory is TLS handshake fingerprinting is most likely, but Bartek proposed a bunch of other possible ways, so who knows. (In reply to Bartek Sabat from comment #0) > I'll be creating a ticket on SoundCloud's end, but I doubt it will get > resolved, because it'd require them to "reduce" their "security" in order to > support a very small subset of browsers. You're likely right, but we can hope for better. Make sure they understand that WebKitGTK is part of upstream WebKit, and maybe point them to this bug report so they understand we are discussing. Currently we do not have a policy for how WebKit should deal with such issues. I will soon propose an antidiscrimination policy to help WebKit address such issues in a more aggressive manner. Some aspect of this might be improved by the Navigator.plugin changes to match spec in Bug 245396. |