Hi everyone, in latest HEAD you will find a new native protocol option
named --https-socket.

This is like --http-socket but (obviously) with ssl support.

All of the same rules of --https apply (included sni and sessions shared
caching), with the (again obvious) difference that there is no proxy in
place.

The main usage will be putting uWSGI directly behind a tcp proxy (haproxy,
uwsgi-rawrouter, ...) or for ssl-certificate authentication in intranets.

Expose it to the public network only if you know what you are doing.

Special note:

the protocol is (as expected) async friendly, so Coro::AnyEvent, gevent
and friends will work out of the box

-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi

Reply via email to