Module config.py's create_ssl_context ssl_version param validate to int alone

[Murugaraju]

Description of problem

Hey Team,

I had some settings for the gunicorn config in saved in cfg file. First scenario is the execution of gunicorn is done via shell file, the file containing the code as below

exec su -p randomuser -c 'gunicorn --ssl-version=5 --certfile=../sample/server.crt --keyfile=../sample/server.key  -c app/gunicorn.cfg app.__main__:app'

During above scenario the execution of gunicorn done via the worker UvicornWorker. The problem found is as below

Second I moved the --ssl-version=5 from command arg to cfg file as below

ssl_version = 5

it worked.

uvicorn/uvicorn/config.py

Line 106 in 22873a9

ssl_version: int,

Any chance that this explicit annotation to ssl_verification can be removed. Thought of giving the team a visibility on the scenario I faced 😅

[frobnitzem]

In using uvicorn with SSL, I've noticed a few of these kinds of issues.
I think the solution should be to require these inputs have the correct enum type defined by python's ssl module:

• PROTOCOL values
• VerifyMode

For example, the uvicorn documentation just says verifymode is an int, but not that verifymode 1 makes client certificates optional.

Using strings would make these choices much easier than integers.