Upgrade connection from HTTP to HTTPS

[daxpedda]

I have a case where I want to host a server on a non-standard port, like 8000 for example.

What I want is that users enter asd.com:8000 and it would lead them directly to the server, which currently isn't possible in combination with tls, because most browsers automatically connect to http by default, which will be denied.

So my question: is upgrading from http to https without having to provide your own TlsAcceptor in the scope of warp?

I'm already working on a PR.

[seanmonstar]

It sounds like a good feature! Perhaps optional, since if someone has taken care of this outside warp, no need to pay the cost.

[daxpedda]

Perhaps optional, since if someone has taken care of this outside warp, no need to pay the cost.

Agreed.

Sadly my endeavours into this have failed. Can you give me any pointer on how this could possibly be implemented?

I tried going through TlsAcceptor and I understand the part that returns a failure, but it seems that the failure is ultimately handled in hyper::Server. Following the trail there, it seems hyper::Server does have no functionality to handle a failure like that by sending a header back, am I correct with this assumption?