Gunicorn worker ssl

[tumb1er]

What do these changes do?

gunicorn provides SSL support for sync workers and for gaiohttp worker for aiohttp.
aiohttp provides GunicornWebWorker, but it lacks SSL support.
This PR allows GunicornWebWorker to init SSL from gunicorn config.

Are there changes in behavior for the user?

No regressions expected

Related issue number

Nope

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes

[coveralls]

Coverage increased (+0.003%) to 97.971% when pulling 0f0b392 on tumb1er:gunicorn_worker_ssl into 072991f on KeepSafe:master.

[asvetlov]

What is your use case?

From my understanding people starts Reverse Proxy server like Nginx, push Gunicorn behind its and start aiohttp workers under gunicorn.

In this scheme only Nginx serves SSL/TLS connections, all internal communications are insecure and uses raw sockets, isn't it?

[tumb1er]

My use case is uploading huge files over ssl (without nginx).
With nginx serving connections, it first dumps full request to disk, then reads it and pass to upstream (aiohttp). Yes, nginx support client_body_in_file_only but it is useless in case of multipart requests.

[asvetlov]

Ok, makes sense

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.