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

verify_ssl for aiohttp.request #127

Closed
wabu opened this issue Jul 22, 2014 · 5 comments
Closed

verify_ssl for aiohttp.request #127

wabu opened this issue Jul 22, 2014 · 5 comments
Labels

Comments

@wabu
Copy link

wabu commented Jul 22, 2014

I did not find a way to pass verify_ssl to aiohttp.request. It somehow seems implemented in ClientRequest and TCPConnector, but it is not passed on in aiohttp.request.

A workaround for now is to pass connector=aiohttp.TCPConnector(force_close=True, verify_ssl=False), but it's not very usable.

@fafhrd91
Copy link
Member

passing connector is proper way of passing verify_ssl, if we add verify_ssl to aiohttp.request() it'd add ambiguity with connector parameter.

i am -1

@asvetlov what do you think?

@asvetlov
Copy link
Member

I agree that verify_ssl should live in connector ctor.
Default behavior is verify_ssl=True, that's reasonable one.
If you need to disable ssl check please use explicit connector object.

@amfarrell
Copy link

One challenge this causes is needing to make sure that connector always gets properly closed.

@popravich
Copy link
Member

@amfarrell, you can use connector with ClientSession and it will close the one properly.

@lock
Copy link

lock bot commented Oct 29, 2019

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.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants