4 ms·
I had no idea this was limited to chrome, but having run into it two days ago, changing the user-agent string fixes it completely. I specifically used Android
by anologwintermut 14y ago
I had no idea this was limited to chrome, but having run into it two days ago, changing the user-agent string fixes it completely. I specifically used Android 4.0.2 (Mozilla/5.0 (Linux; U; Android 4.0.2; en-us; Galaxy Nexus Build/ICL53F) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30).
- jordanbaucke 14y agoHmmm I was going to investigate. So that seems to point to T-Mobile doing some sort of spying on one's HTTP requests? If that's the case why not block other non-mobile user-agents?