Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix aiohttp client for verify_ssl=False #8507

Closed

Conversation

bpicolo
Copy link

@bpicolo bpicolo commented Jul 30, 2018

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: 3.0.0 branch for changes related to OpenAPI spec 3.0. Default: master. (I'm guessing I'm doing it right? This is general rather than 3.0 related)
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language. (@kenjones-cisco)

Description of the PR

The async client is currently broken if verify_ssl is False, because aiohttp raises an exception if both verify_ssl is False and an ssl_context is passed to the client:
https://github.com/aio-libs/aiohttp/blob/5d5bb4674d11a9a2576266a1a51174af551262eb/aiohttp/client_reqrep.py#L120

Ergo, this makes sure we don't pass an ssl_context when verify_ssl is false.
Happy to add any tests you think might be necessary, just let me know what would be best - unfamiliar with working in this repo :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant