查看更新
我正在尝试使用自签名证书将请求发送到Web服务器（在未自签名的网站上正常运行），并且不断收到错误消息：
SSLEOFERROR EOF occurred in violation of protocol
相反，在使用请求时，用于python的非异步http客户端（将ssl_verify设置为false可以成功连接到服务器）。但是，异步http客户端问，缺少这种功能，我得到了SSLEOFERROR。
Asks确实允许接受自定义的ssl.SSLContext对象，但是经过多次尝试，甚至将自签名证书添加到我的本地密钥库中，没有任何事情导致成功连接，并且错误保持不变。
import asks
import trio
from asks.sessions import Session
url_list = ['facebook.com', 'https://example.com']
results=[]
ssl_context=ssl.SSLContext()
ssl_context.verify_mode=ssl.CERT_NONE
ssl_context.check_hostname = False
async def grabber(s,url):
r=await s.get(path='/'+url)
results.append(r)
async def main(url_list)
s = Session(connections=2,ssl_context=ssl_context)
s.base_location='https://self-signedcert-site/'
s.endpoint='path/to/restapi'
async with trio.open_nursery() as n:
for url in url_list:
n.start_soon(grabber, s, url)
trio.run(main,url_list)
结果如下（手工键入的跟踪..无法从错误的计算机共享/粘贴）
开始SSLEOFERROR追溯：
Traceback (most recent call last):
line 463 in _retry
ret = fn(*args)
line 718 in read
v= self._sslobj.read(len)
ssl.SSLEOFError: EOF occured in violation of protocol (_ssl.c:2508)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
line 90, in runcode
exec(code, self.locals)
File "<input>", line 28, in <module> run.py line 1783 in run
raise runner.main_task_outcome.error
file"<input>", line 26 in main
file _run.py, line 725, in __aexit__
raise combined error_from_nursery
file"<input>", line 15 in grabber
File "asks/sessions.py", line 253, in _handle_exception
raise e
File ...asks\sessions.py" , line 186 in request
sock,r = await req_obj.make_request()
file ...request_object.py ", line 217 in make_request
response obj=await self._request_io(req, req_body, hconnection)
file ..request_object.py", line 254 in _request_io
response_obj = await
self._catch_response(hcconection)
file ..request_object.py", line 596, in _catch_response
data=await self._recv_event(hcconection)
file "...request_object.py", line 618, in _recv_event
(await asynclib.recv(self.sock,10000)))
File "..._event_loop_wrappers.py", line 47 in trio_receive_some
return await sock.receive_some(max_bytes)
file "..._ssl.py" line 657 in receive_some
return await self._retry(self._ssl_object.read, max_bytes)
File"....trio\_ssl.py", line 468 in _retry
raise trio.BrokenResourceerror from exc
Trio.BrokenResourceError
更新
我发现了一些东西。
如果我只使用
asks.get()而不是使用会话对象，那么我就能看到响应中的细微变化：问图书馆
SSLEOFERROR：[通过使用pip安装问题解决了错误-conda-forge正在运行3个发行版]
asks.get('https://url', auth=BasicAuth(usr_pw))无效的HTTP响应错误：
asks.get('https:url/rest/api/path',auth=BasicAuth(usr_pw))页面正文按预期返回：
asks.get('https://google.com')请求库
页面正文按预期返回：
requests.get('https://url', auth=HTTPBasicAuth=(usr_pw),verify=false)API正确返回了预期的响应：
requests.get('https:url/rest/api/path', auth=HTTPBasicAuth=(usr_pw))考虑到我会产生另一种错误（无效的http响应），我为此添加了更多的追溯
开始无效的HTTP响应回溯：
[完整路径已删除]
File "....\asks\sessions.py", line 185, in request
sock, r = await req_obj.make_request()
file ....\asks\request_object.py", line 214, in make_request
response_obj = await self._request_io(req, req_body, h11_connection)
file "...\asks\request_object.py", line 251, in _request_io
response_obj = await self._catch_response(h11_connection)
file"...\asks\request_object.py", line 599, in _catch_response
assert isinstance(endof, h11.EndOfMessage)
AssertionError
The above exception was the direct cause of the following exception
[some output redacted]
file "...\trio\_core\_run.py", in 1783, in run
raise runner.main_task_outcome.error
file "...\my_script_thats_having_this_error, line 33, in main
n.start_soon(grabber,s)
File"....\trio\_core\_run.py", line 725 in __aexit__
raise combined_error_from_nursery
File "...\my_script_thats_having_this_error, line 30 in request
r = await s.request(method, url=uri, **kwargs)
File "...\asks\sessions.py", line 215, in request
await self._handle_exception(e,sock)
File "...\asks\sessions.py", line 253, in _handle_exception
raise BadHttpResponse('invalid HTTP response from server. ') from e asks.errors.BadHttpResponse: Invalid HTTP response from server.
最佳答案
我尝试使用asks v2.3.5使用自签名证书连接到站点，但成功成功：
>>> trio.run(asks.get, "https://self-signed.badssl.com")
<Response 200 OK>
这是一个严重的错误...这意味着默认情况下，问号实际上具有与
verify=False等效的设置。我希望可以在接下来的几天内紧急发布以解决此问题。请参阅：https://github.com/theelous3/asks/issues/134 [编辑：此问题已在Asks v2.3.6中修复。]但是回到您的问题！鉴于默认情况下，
verify=False会问，我认为自签名证书不会引起您的问题。无论如何，自签名证书应导致SSLCertVerificationError，而不是SSLEOFError。不幸的是，我认为这里没有足够的信息来找出您的实际问题是什么：-(。
SSLEOFError异常表示服务器突然关闭了它们的连接。也许握手有问题吗？被配置为提供一组不同的密码套件，并且服务器不喜欢Asks的产品吗？虽然这些都是疯狂的猜测：-/。我可能会尝试使用Wireshark来了解实际情况。