loading...
Cover image for Beware! Catalina update forcing HTTPS

Beware! Catalina update forcing HTTPS

crimsonmed profile image Médéric Burlet ・1 min read

Today we lost 1h of time battling to understand why https wasn't working.

Thank you Apple

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: http://127.0.0.1

Somehow Chrome kept giving us a connection refused same for Safari. When we checked the URL we could see that it was forced to https.

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 localhost, 127.0.0.1 (way to be annoying).

Solutions:

  • Boycott the Catalina breaking update
  • Go to Preferences -> Privacy -> Manage website data -> remove 127.0.0.1

Conclusion:

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.

Posted on by:

crimsonmed profile

Médéric Burlet

@crimsonmed

『  』| Passionate Coder | Idea Hurricane

Discussion

markdown guide
 

@adam Crockett I'm not hating on Apple, I just don't like being forced into something. Kinda reminds me of some of the tactics Microsoft pulled. And as far as Google Chrome blocking http, I uninstalled it awhile ago.

@FultonB I that's an option, I've been strongly considering.

@Burlet I hear you. Unfortunately I have 64-bit installed(came preinstalled). What stinks is some apps I would like to use are only 32-bit.

 

I'm not condoning apple, but I am because http is going the way of the dodo, if chrome (and it will, officially announced) blocks http, any http projects are pretty much scrap at this point. Apple is dragging us into a new era, everyone hates on Apple then everyone just copies in a year or so when the heat is off.

 

I'm not saying it's a bad thing but I don't see why they couldn't be more straight and make this information clearer. To be able to see how to whitelist I had to find a lost comment on a thread on one of apple's forums.

 

The update is kinda awesome but they should have considered local development environment...a good solution is for Apple to add ability to whitelist domains which includes all connections from localhost by default.

 
 

Where's the boycott petition? I'll be the first one to sign it! An aspiring dev...

 

I have to admit I've been pushing back Catalina update for a while. Many apps I have and use like Lightroom I have in 32bit version and I have been lazy to find the updated versions.

 

our electron build process got messed up too. we have to upgrade, and some error when building windows on mac.

 

Is the same thing with certain domains on chrome like .dev .app was driving me insane for hours and finally installed a cert on my server and then it worked. Removing the s didn't do anything.

 

That's a shame. I'd like to try out swiftUI at some point.. but not while my job requires me to working on web apps most of the time 😕