[Twisted-web] Enforcing SSL for non-SSL requests
tv at twistedmatrix.com
Wed Aug 10 22:31:55 MDT 2005
Marek Habersack wrote:
>>Your SSL problem has to do with trying to talk non-SSL protocols to an
>>SSL port, as mentioned elsewhere in this thread.
> Yes, I know, the client isn't starting the SSL handshake when it is expected
> to - the real question was how to work around it using a single port (my
> client's requirement), but it seems I will have to use the standard two-port
> approach here.
For HTTP, you can't do it (cleanly).
For SMTP, IMAP, POP, LDAP, etc., use STARTTLS.
For your own protocol, add a STARTTLS feature to the protocol.
More information about the Twisted-web