Friday, I tried the first time to register my phone (/e/ version 0.13-2020120889008) to the WIFI inside the ICE. It was rejected with a comment containing something like “use a contemporary browser”.
This message doesn’t sound logical to me as it was working with my BlackBerry 10 device until I stopped using it: Its browser was much less “contemporary” and already had problems loading or displaying many websites.
For the browser on /e/OS, this was the first time I got a reject like this. I did discover that half a year after swithing to /e/ because I mostly sleep or read real paper in a train…
Has anyone else tested to connect to WIFI in an ICE? Was it successful or not?
Edit: my gut feeling is that whatever their error message is, it’s probably the part before the “use a contemporary browser” that’s relevant. Unless of course that’s a generic “your browser is too old” or so
I understand: either the router is confused or the system hides too much. The latter was already my assumption. I’ll check what happens exactly when I’m travelling next time. The “user agent” is indeed confusing but I didn’t manipulate it
What I don’t understand here is: the wifi did reject a browser???
When the wifi environment is indeed involved (this means: when the same web request works without any errors when your’re outside of this wifi) it must have a routing of HTTP requests over an own HTTP proxy which filters requests by header contents. - Is this thinkable? OK, this would be a great chance to log all the traffic … But why are requests rejected?
Yeah, that User Agents looks rather “normal”. A Chrome Browser on desktops is almost the same, except that “(Linux; Android 9; Unspecified Device)” is “(Windows NT 10.0; Win64; x64)” as an example on my laptop. Or “(Linux; Android 10; FP3)” on stock ROM of my FP3.
But I don’t know if that would be accepte by ICE WiFi