Hacker News Reader

Comment by windexh8er | Hacker News Reader

This has been going on for a while:

https://mobile.twitter.com/xdaroj/status/1090319095134867459

It's interesting that Windows 7 and Chrome 72 doesn't work as well. Using Browserling, and httpbin to get the headers this combination doesn't work either:

https://www.browserling.com/browse/win/7/chrome/72/https%3A%...

Here's a screenshot of the headers by that Browserling instance type: https://imgur.com/a/Z7bGbpm

This has been going on for a while for a SaaS called “Browserling” that appears, from the thread, to emulate or host a browser of some sort in the cloud somehow.

Does this issue affect normal Linux desktop-hosted locally-operated “the standard way” browsers?

Just tried it on my locally hosted Arch Linux desktop. It doesn't work. Firefox, Chromium. Doesn't matter. Doesn't work.

That was the point of the Twitter interaction. A way for Apple to repro easily, but they ignored. I can't believe this has gone on so long quite honestly. Then again it really shows the ecosystem lock-in. This is a great example though... Eventually why not lock out everything non-Apple? Hasn't seemed to have mattered much over a month.

I don't think the person who brought it up was aware the issue was associated with the Linux/X11 user agent, unfortunately, so couldn't provide support with the right information to actually reproduce the issue in a useful way. Still, it shouldn't have been an issue for this long, and who knows when they'll actually get around to fixing it. I don't think they're in a hurry to help Linux or Android users.

I would disagree. It is not the end users job to hand an organization like Apple the issue on a silver platter. The user presented a 100% reliable reproduction of the issue to Apple Support. Apple ignored it and defending them by saying it wasn't presented in a "useful way" is, in my opinion, diminishing both what was brought to Apple in a relatively complete way and Apple failing to simply acknowledge or understand there is a problem.

I agree it likely won't be fixed anytime soon. It probably impacts single digit (or less) percentages of their users.

Did he once mention what kind of OS, phone or device he was using? There's like no actionable information there.

Indirectly, yes - they did. All of this information can be deduced from the browser in Browserling that was referenced as working example to reproduce the error. There are many actionable data that can be deduced given what was provided to Apple.

While there are many others, the site below [0] could have been used from the Browserline instance in question to deduce header information which would have included the OS as you've requested. Someone in Apple Support could likely figure this out given that information and ability to reproduce.

[0] https://httpbin.org/#/Request_inspection/get_headers

On elementaryOS it also gives the 502 Bad Gateway on both Firefox and Epiphany.

It's working today!

It doesn't work on Firefox 65.0.1 on Arch Linux, but it works perfectly with exactly the same browser version on FreeBSD. I guess they are filtering everything that specifically says "Linux"

Excellent, thank you for that.

I've checked browserling and it spins up a browser in a hosted VM.

Which browser?

Reply on news.ycombinator.com