@kelunik Thank you for looking into, this looks interesting!

There's also #53 which discussed always enabling TLS by default and making encrypted and unencpryted connections work on the same port. What do you think about this?

@clue There have been vulnerabilities and weaknesses due to one port being used for both. I think these were mostly due to the client using opportunistic TLS, so they might not be applicable if the client knows whether it wants to use TLS or not. Maybe @paragonie-scott has some input here.

@clue Even if both might be used at the same port in the future, there should be a way to force TLS being used.

We can add same port plain and TLS later using http+https as scheme or similar.

@clue What's required to get this in?

@kelunik Thanks for the friendly reminder. I'd rather not rush this and break this feature again in the future. Instead, I'd like to properly address the underlying feature request in #53 (which in turn depends on reactphp/socket#89 and possibly others).

Rest assured, this is definitely on the roadmap and I'm planning to pick this up as soon as time permits. In the meantime, you can always keep using your forked version.

I hope this helps 👍