-
Notifications
You must be signed in to change notification settings - Fork 88
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
when use client.request to send a request to https url it falied with SSL3_GET_SERVER_CERTIFICATE #60
Comments
in the source code : so how can I transfer this parameter into the client.request(op(body={})) |
Hi, good work & finding. Those client implementation are made for common cases. One possible remedy for your case is to add an additional parameter when constructing the client object: from pyswagger.contrib.client.requests import Client
client = Client(auth, verfiy=False) # the new way All requests sent through this client would skip verification of ssl certificate, what do you think? |
Thanks mission-liao. |
OK, I would provide a fix on it next Monday, should be an easy fix. |
The fix would be included in next release, but right now, I'm still waiting for another PR for 'extensible content-type'. |
- #60 - it’s helpful to test server before production.
This options required by requests.Session.send could be passed when constructing pyswagger.contrib.client.requests.Client from pyswagger.contrib.client.requests import Client
client = Client(send_opt=dict(verify=False)) |
- customised codec: pyopenapi/pyswagger#49 - support for no SSL certificate pyopenapi/pyswagger#60 - renders failed on windows pyopenapi/pyswagger#63
the error message like the following:
requests.exceptions.SSLError: [Errno bad handshake] [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]
when I new the client and send the request , can I add a parameters like "verify=False"?
I can use this parameters in requests.get()
The text was updated successfully, but these errors were encountered: