2 ms·
The user-agent parsing is fast, it's the server-side rendering logic specific to Linux user-agents that is somehow terribly slow.
by ohitsdom 10y ago
The user-agent parsing is fast, it's the server-side rendering logic specific to Linux user-agents that is somehow terribly slow.
- soundwave106 10y agoAnecdotal experience... but when I use Chrome and switch user agents to a random one that probably wouldn't be too common (in my case, Mozilla/5.0 (X11; OpenBSD i386) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.125 Safari/537.36), in Chrome Network tools it seems that there were several Javascript pages that were being loaded through a "StaticLoad.aspx" (namely WordEditor.js and Hermes.js scripts), that simply hung while downloading. Changing the version didn't seem to matter (I couldn't find the latest one for any Linux style OS easily, but I tried "Mozilla/5.0 (X11; OpenBSD i386) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36" with the same results). However, Android type user agent strings like "Mozilla/5.0 (Linux; Android 4.0.4; Galaxy Nexus Build/IMM76B) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.133 Mobile Safari/535.19" load fine. Not knowing the code I have no idea what this could mean, but I suspect you're 100% right here, there's some server side rendering that does different things based on user agents, and it's having trouble on the "other UA" category for some reason.