Today we lost 1h of time battling to understand why https wasn't working.
We were dockerizing some old projects as AMPPS that we were using for them is becoming not supported with the new Catalina update.
The issue is we had just quickly done a setup mysql + apache for the docker container and were trying to access:
Somehow Chrome kept giving us a connection refused same for Safari. When we checked the URL we could see that it was forced to
Of course we tried simply removing the
s from the URL but it was of no use.
This led us to understand that now by default Apple forces https for
127.0.0.1 (way to be annoying).
- Boycott the Catalina breaking update
- Go to Preferences -> Privacy -> Manage website data -> remove 127.0.0.1
Forcing people to move to 64bit apps as well as forcing https without warning the users can be quite troublesome. Especially in the development world as for our part, doing webdev, it made us think our docker wasn't working that we had messed up and this resulted in us stopping our activities temporary while we finally understood that the update made radical changes to how the dev environment was working.