This is Microsoft’s documentation on redirect local host exceptions. It looks like they allow ports to be specified. I wont be able to the Azure OAuth2 on the DO deployment until tomorrow.
Redirect URI (reply URL) restrictions - Microsoft identity platform | Microsoft Docs
I use MAMP Pro and that includes SSL for localhost.
Maybe it is something MAMP does in your hosts file, any chance your hosts file looks different to this semi standard one.
My hosts file is structured just the same as yours. Nothing extra.
Not sure whether this is relevant or not, though, but I create hosts for each project so use things like https://projectname.local or just https://projectname as the domain.
Still cant figure this one out after reading about 10 different articles, lol. @George, being a fellow mac mac user and a thousand times smarter than me, do you have any idea how to make my website show on https://localhost instead of http://
I am going to stop fiddling with this, at this rate I am going to be reinstalling my entire operating system, the installation of certificates to mac system keychains etc. is a little beyond the scope of my knowledge.
Maybe the Wappler team could add this into their docker local automation somehow in the target settings for those API where its needed such as
The local NodeJS server we run for Wappler or tge one with docker for development are http only.
There is actually no need to run SSL (https) for localhost. It will only slows you don’t and also will require additional port to be open. As well also have local self signed development certificate for SSL.
So on your port 8100 runs just http server.
Might this help?
https://medium.com/responsetap-engineering/nextjs-https-for-a-local-dev-server-98bb441eabd7
Or this?
If you need secure HTTP to your local machine without the hassle you can run a Cloudflare argo tunnel for free. It’s basically a free alternative to ngrok but on your domain.
https://blog.cloudflare.com/tunnel-for-everyone/
You just run a service in your local machine that tunnels your connection through CF network. You create a cname for a domain you own in CF dashboard and you can access or give access to a client via CF secure network. Without having to worry about your firewall or installing certificates.
So if you have a domain laying around just plug it in CF create a cname that points at the url the argo tunnel desktop service creates for you et voila.
You can access your project via something like https://dev.mydomain.com
It’s actually part of my setup. Say I am developing an app called mycoolapp which lives in mycoolapp.com
https://mycoolapp.com points to my production server.
https://qa.mycoolapp.com points at my staging server where my clients can test anything prior to being moved to production.
https://dev.mycoolapp.com points at my local machine where I can show quickly something to the client to get it validated by them before continuing the development. I run the CR argo tunnel only when I’m going to demo something. The rest of the time is not running.
I know one reason - is to enable WebRTC.
You are not allowed to run webrtc on http after Chrome 47+.
I know that there is workaround for this, but yet still.
