4 ms·
It does seem unlikely, but playing with the example UA in curl (as noted in https://news.ycombinator.com/item?id=38925015 https://news.ycombinator.com/item?id=3
by aragilar 3y ago
It does seem unlikely, but playing with the example UA in curl (as noted in https://news.ycombinator.com/item?id=38925015 https://news.ycombinator.com/item?id=38925015) seems to show it's the combination of "Android" and "Firefox" that causes this behaviour. I wonder if any other mobile browsers are broken?
- kevincox 3y agoA far more likely explanation is simply that two features or workarounds are enabled, maybe "Android" triggers a prompt to install Chrome or something and "Firefox" triggers some workaround code. However these interact poorly and cause a crash. If they wanted to sabotage Firefox I doubt they would choose to send a blank page. They would probably send infinite captchas or just disable most features (which they already do).