🔀 Add support for HTTPS dev server - #175

Does the port have to be separate or could we handle https traffic on the same port as insecure traffic?

Does the port have to be separate or could we handle https traffic on the same port as insecure traffic?

Well HTTP and HTTPS are separated protocol. By default it's 80 and 443 and they don't start in the same way.

Maybe the server could detect if the client try to start a new TLS session and it could than switch from regular HTTP to HTTPS traffic but I feel we would need to ditch mist (or ewe) to directly listen to the TCP socket to do those kind of hack.

What I mean is generally HTTP and HTTPS are on different port since they are kind of their own different service. If I take vite and enabled https. It will just replace the http:// with https:// and make the server incompatible with http://.

I only saw projects like Caddy or Nginx that would detect if the traffic start with TLS or not and that's generally just for redirecting the user to HTTPS.

If I take vite and enabled https. It will just replace the http:// with https:// and make the server incompatible with http://.

This sounds ok to me, if you're opting into https you probably wont open the http version anyway right?

If I take vite and enabled https. It will just replace the http:// with https:// and make the server incompatible with http://.

This sounds ok to me, if you're opting into https you probably wont open the http version anyway right?

I need to think more about this because it’s kind of depend. Like for when I did needed use https I did generated with mkcert a personal CA certificate that I did install on my dev device to trust it but if I don’t (or can’t install) I know the not secure port is also still useful.

But yeah is having both HTTP and HTTPS available at the same time is useful or fully switched to HTTPS would be preferable. Like said I need to think a little more

Yah I think you are right and just having like every other dev server adding the Cert and Key should just switch from HTTP to HTTPS. (so I updated this PR to reflect this)

I guess you could always run it twice if you want the non-https one too.

Should be okay now. At least it depend if you find the new documentation and errors message could be improve ^^ (I hate writing english documentation)