cant use dispatcher locally because of SSL

[TB3dock]

We have 7 AEM cloud instances.  The vhosts files are complex, and we have issues with redirects etc.

Testing by uploading to cloud takes 1-2 hours, so it takes a day to test a few changes.

We want to run dispatcher locally. It obvoiusly requires editing the  /etc/host file with the name one of our sites, e.g.

127.0.0.1 www.mysite.com

Then when we hit http://www.mysite.com:8090 or https://www.mysite.com  in a browser, we get:

ERR_SSL_PROTOCOL_ERROR

because there are no certificates etc installed.

Has anyone solved this issue?

In the vhosts, everything is "http". this means we see constant switching between SSL and non SSL whenever a rewrite rule happns, which means browsers see a lot of unnecessary redirects, which certainly affects performance and SEO.

To try to fix this, we have puth https:  in may of the rewrite rule targtes, but this doesnt seem to help

[Asutosh_Jena_]

Hi @TB3dock 

If you are using Mac OS, then you can generate Self Signed SSL cert and it can be installed on the keychain. 

Once it's installed, you can configure your local dispatcher with HTTPS i.e. with port 443 and can simulate the exact use case like how it works on the production URL.

Everything will be same only, the cert will be Self Signed. I personally use the same approach on my system.

Please follow the below URL to generate the SSL cert and install on Mac:

https://devcenter.heroku.com/articles/ssl-certificate-self

Thanks!

[TB3dock]

Thanks for the reply.  With cloud aem, our dispatcher configs only have http.  We assume that the cloud has some sort of https termination infront of the dispatcher (WAF may be).  The crux is that our vhosts for cloud have not https config (that we know of), and we cant modify them or it will break production.  Any suggestions?