2

UPDATE (2022-12-23): turns out the issue is caused by ISP (more specifically, all ISP's in Egypt at the time of writing), and everything works as expected when I'm connected over VPN.

This is a weird issue that has been going on since the release of Safary 15.

It does not connect to any website over http, even if the site redirects to https. It simply times out and says “couldn’t connect.”

I’ve tried:

  • deleting cooking and site data.
  • clearing history.
  • disabling extensions.
  • resetting HSTS, and deleting safari folder.
  • macOS safe mode.
  • testing on an entirely new macbook and a clean install of macOS

I haven't tried reinstalling OS or creating a new user yet, because I cannot do that at the moment due to time constraints.

EDIT 1: Problem persists with newly created user.

Safari 15 has been doing that since its release on BigSur and still on Monterey.

It doesn’t matter if I open website from address bar or click a link in a page.

I think it has to do with the new HTTPS redirection.

It’s really frustrating, any suggestions?

P.S.

  • I don’t have a proxy, it’s a home network, and I do not use VPN.
  • I does not work no matter what network i’m connected to, and the same websites open fine in firefox.
  • Some sites are not operating over https, some have both and redirects http to https, but if I click a link or attempt to open URL with http, it does not open. I have to copy the link and open in another browser.
  • Some websites—especially academic—do not have SSL, so it's really important for me to have it working over unsecured HTTP.
  • I do not have Adguard or any other safe guard apps that might be manipulating my connection routing the traffic elsewhere.

EDIT 2: Wireshark dump (Safari rquest)

EDIT 3: Wireshark dump (Firefox rquest)

NOTE: Sites work fine on Safari on iOS, on same network.

1 Answer 1

2

UPDATE

Given your update and the Wireshark dump I requested, it is clear that the problem is not with your Safari browser. The browser does send the request for the site in the HTTP protocol (non-encrypted). However, it never receives a reply from the server.

You need to look at any software you have installed that could interfere with network requests, devices on your local network (routers, firewall, VPN gateways, etc) as well as what your internet provider does to your traffic. If you have a secondary computer, tablet, etc it would be worth testing that on the same network.

OLD ANSWER

I'm not sure I'm convinced that this is caused by the automatic HTTPS upgrade (I cannot see why it would) - but if you believe this to be so, I would suggest trying to disable that feature.

First you need to enter Safari Preferences, click on the Advanced tab and then put a checkmark for Show Develop menu in menu bar.

Then from the Develop menu in Safari, under the Experimental Features submenu, you can disable Automatic HTTPS Upgrade.

If you haven't got this option, I would try installing Safari Technology Preview and try the same!

24
  • 1
    The whole point of the HSTS preload list is that these sites will only be accessed over TLS/SSL/https. I think you should continue with Wireshark as that would give valuable insight into the actual cause of the problem.
    – jksoegaard
    Commented Dec 15, 2021 at 17:29
  • 1
    Okay, so now we can conclude that it is not the fault of the browser (unless you’re misreading Wireshark). You need to look at any software you have installed that could interfere with network requests, devices on your local network (routers, firewall, VPN gateways, etc) as well as your internet provider. If you have a secondary computer, tablet, etc it would be worth testing that on the same network.
    – jksoegaard
    Commented Dec 17, 2021 at 8:24
  • 1
    Yes, you could add the dump as a link to the question for example - or a few screenshots. But it seems that the request is being sent from the browser, it goes out the of the network interface, but no reply comes back - that means the problem is external.
    – jksoegaard
    Commented Dec 17, 2021 at 12:51
  • 1
    You say that it works in other browsers - I think this is news to us. Do you mean that if you open Firefox, Chrome or similar and access the exact same airliners site on HTTP (non-HTTPS) - you can get the site to work? - Without using SSL? - If so, please make a Wireshark dump with that second browser. Then it is possible to compare for differences.
    – jksoegaard
    Commented Dec 17, 2021 at 16:24
  • 1
    I have tested airliners.net in Safari with "Automatic HTTPS Upgrade" turned both off and on - it works fine in both cases.
    – jksoegaard
    Commented Dec 17, 2021 at 16:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .