fixing step-05 and step-06 enabling ssl in node.js about webrtc-web

[samdutton]

Thanks @EderNavarro! Just looking into this now.

[nitobuendia]

I am currently checking this. The solution proposed by @EderNavarro seems to work :) Thanks a lot!

I have been able to deploy localhost with https and connect my phone through it (whereas with http version it rejects the API calls).

I think the best proposal here would be:

1. Adding a section to step-05 (step 7 of Codelab) explaining why https connections may be required (multiple devices, running on a server). This section will also describe what changes are required to change from http to https.

2. Adding the relevant lines of code to the codelab, but commented out and with clear explanations of what to comment / uncomment if you want to run over https.

My only concern at the moment is how to generate a valid certificate for localhost. Testing a bit with openssl and a few other ideas. For servers, I would suggest a link to Let's Encrypt can be it.

[nitobuendia]

Same as #32:
A quick update here: we are working on fixing this by serving the codelab on https so it can be tested across devices deployed in localhost, but also is more or less prepared to go to a server with minimal changes. There are a few things that need to be fixed first, hence it might take a bit, but on the pipeline. Thank you for reporting and the patience here.

[samdutton]

Can't remember if I suggested this elsewhere — would Surma's HTTP/2 server (which provides HTTPS, though with certificate warning)?

https://github.com/GoogleChromeLabs/simplehttp2server

[nitobuendia]

@samdutton We discussed this, yes. I do not think there is need for that. node.js is enough and provides a solution with the same warning. The solution is coded and the text is prepared. The main issue we faced is the servers that were used only for the codelab; for which we still do not have a solution.

[samdutton]

@nitobuendia OK — thanks.