Redirect http to https

[steteb]

Hello,

I saw following discussion:

#2183

I have a similar request, but the problem is that I have the web server listening https on a custom port, so I cannot use port 80 with its event handler to redirect and port 443 is not used for https. How can redirect a request http from the browser to https in this case ?

maybe using mg_url_is_ssl() to know if the browser request is http or https and manage this in the event handler ?

I am using Mongoose version 7.16

Thank you

[scaprile]

Let me see IIUC.
You have a listener that expects HTTPS, that is, it is ready to call mg_tls_init() on connect and will initiate/process a TLS handshake after that, and handle incoming data over TCP as TLS records.
You want that listener to "guess" that what is coming is not a TLS handshake or a TLS record but an HTTP message.
I don't see such a thing is possible. mg_url_is_ssl() does not work on the request, it works on the URL you pass as an argument, it can't whatsoever know if the browser request is HTTP or HTTPS, because there is no such thing as "an HTTPS request", HTTPS is just HTTP over TLS, so you first start a TLS encrypted pipe, then send HTTP over that pipe. You would need to compare HTTP to TLS
The answer is the same given in the discussion you link, we can't do anything other than process what we were configured to process, and you can't process two different types of data simultaneously. No matter what port number you use, that is irrelevant, you either handle HTTP and send a redirect to the HTTPS port, or you start TLS and process HTTP inside that flow (and maybe send a redirect to the HTTP port if, for some reason you would want to ever do that).
If that is not useful to you, then you have to start a raw TCP listener, process the incoming data yourself, decide whether it is HTTP or a TLS handshake, and then reconfigure on the fly. I'm not sure that would work, because I would expect a server to start TLS with a Server Hello, and you wouldn't be doing that, because you would be waiting to see what the other end sends. I'm not a TLS expert, though.
AFAIK, you need two ports. Number them as you wish.

[steteb]

ok, thank you, I got it