1854352 - linkedin.com - Wrong domain accessed when using Mozilla VPN

Status: RESOLVED WORKSFORME

(Mozilla VPN :: Client for Linux, defect)

Description

[Raul Bucata]

From github: https://github.com/webcompat/web-bugs/issues/127337.

<!-- @browser: Firefox 117.0 -->
<!-- @ua_header: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/127337 -->

URL: https://linkedin.com

Browser / Version: Firefox 117.0
Operating System: Ubuntu
Tested Another Browser: No

Problem type: Something else
Description: While being connected to Mozilla VPN using the Los Angeles location I was constantly redirected to the linkedin.cn website - the chinese version. Only worked properly when I disconnected from the VPN
Steps to Reproduce:
I tried to login to my linkedin account by going to https://linkedin.com but was constantly redirected to the chinese version linkedin.cn while connected to mozilla vpn using the Los Angeles location. The website only worked when I disconnected from the vpn.

<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>

From webcompat.com with ❤️

Change performed by the Move to Bugzilla add-on.

Comment 1

[Raul Bucata]

The issue was reported via the webcompat.com reporter. Since the issue addresses Mozilla VPN, we have moved the issue. Please feel free to move the issue to the correct Product and Component.

Comment 2

[Santiago]

This seems like it was filed by a bot so I'm not sure I'll get an answer. Regardless, this is most likely an issue on LinkedIn's infrastructure (CDN or load balancer maybe), insofar as they are taking a Los Angeles IP for a Chinese one. In fact, Mullvad (our network partner) doesn't have servers in China.

I do wonder if the user-agent has any role here (where the accept-language header may be tripping up the infra).

For what's worth, I just tried using Mozilla VPN to access LinkedIn and didn't get redirected, so maybe it was a temporary fluke.