>> HTTP yes, 127.0.0.1:88
>> Why should I have to have https in my own box?
You will have to ask Google that - that's their policy, not mine.
>> Or better asked:
>> How do I have to test this example?
You can make the connection to localhost secure (albeit with a warning message).
Just by using the certificates tab like any other secure site.
Personally I use a technique Jane Fleming demonstrated;
a) make a DNS entry pointing to your PC. (ie from the internet.)
In my case le3.capesoft.com - at the moment I did this the IP address was 197.242.203.124 (although it does not matter if this is variable.)
b) I opened port 80 in my router, and pointed it at the server on my machine.
c) I ran the "certificates" option on the server, so this went out and got a 90 day cert for le3.capesoft.com
d) I think _changed_ the DNS entry so that le3.capesoft.com now points to my LAN address (192.169.2.11)
Now I can go to le3.capesoft.com from any machine on my lan (including phones on wifi) and it comes out at my, completely secure, LAN server.
Of course it's only good for 90 days - if I wanted a longer cert I'd have to buy one.
>> May you please post the link to the webinar where you showed it?
https://www.capesoft.com/accessories/NetTalkUserGroup.htm #244
Cheers
Bruce