Firefox on my laptop redirects linkedin.com to linkedin.cn
I have a 100% repro rate of Firefox redirecting linkedin.com to linkedin.cn. Unfortunately there's another problem beyond the unwanted redirection: linkedin.cn no longer exits, it has been dead for years, I literally cannot reach LinkedIn at all. It was working fine a week or two ago. How do I prevent Firefox from redirecting behind my back? I see the status message (is that what it's called) in the lower left corner "Performing TLS handshake to www.linkedin.cn" and of course it only times out. I just verified with "Web" (different browser), it connects just fine, which suggests that it's a Firefox issue, not a system wide one.
Alle Antworten (5)
Hi
If you clear your browsing history in Firefox, does that website address redirect correctly?
clearing all history would be very inconvenient :-/ I removed all instances of linkedin from the history - they were all linkedin.com, there simply was nothing about linkedin.cn o.O and it didn't work, it still redirects to linkedin.cn I just verified on my other PC, works fine
Are you using a different DNS server for Firefox and for "Web"?
Does "Web" incorporate a proxy/VPN, which may be allowing it to avoid the redirect?
>>"I just verified on my other PC, works fine" Using what browser?
>>"Does "Web" incorporate a proxy/VPN, which may be allowing it to avoid the redirect?" Can't verify, it crashes when I try to check the settings. But I doubt it, I think it's Xfce4's default browser, and at least builtin VPN seems extremely unlikely.
>>"Using what browser?" Firefox of course
in a bit of a rush now, I'll install another browser later or on the weekend to check what happens there.
You can open More Tools › Web Developer Tools from menu, switch to Network pane, check Disable Cache, next to it in options ("cogwheel") select Persist Logs — and open the full https://www.linkedin.com/ — you can watch the responses and where they come from. That should tell you who initiates the redirection, what host/IP sends that, using which codes etc.
If you suspect they are tweaking the responses based on your user agent, IP, locale etc. you can tinker with all of that, either by editing the headers and resubmitting right in the inspector, or you can try using VPN to give you a different regionality, change the content preferences to english, or use Responsive Design Mode to quickly change the UA string to a different device to see what happens if you look like something else from the outside.