urllib3/connectionpool.py:981: InsecureRequestWarning:

[tashrifbillah]

Downloading REDCap data
/home/tb571/min3-dpdash/lib/python3.8/site-packages/urllib3/connectionpool.py:981: InsecureRequestWarning: Unverified HTTPS request is being made to host 'redcap.partners.org'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
warnings.warn(
2021-06-18 16:11:06,145 - 17044 - lochness.redcap - WARNING - server did not return a content-length header, can't verify response integrity for ('redcap.FAKE', 'FAKE', 'SG99492')
/home/tb571/min3-dpdash/lib/python3.8/site-packages/urllib3/connectionpool.py:981: InsecureRequestWarning: Unverified HTTPS request is being made to host 'redcap.partners.org'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
warnings.warn(
2021-06-18 16:11:06,763 - 17044 - lochness.redcap - WARNING - server did not return a content-length header, can't verify response integrity for ('redcap.FAKE', 'FAKE', 'SG99492')

[tashrifbillah]

@blms , do you know of any elegant solution to this other than the hack?

[blms]

InsecureRequestWarning: I think the only other solution is to follow the certificate verification guide from the documentation. I'm not too familiar with the specific risks involved in suppressing the warning, but it seems to strongly suggest you should follow the guide.

content-length header: I think that can be safely suppressed, otherwise it would have to be fixed by the REDCap engineers to return that header correctly. And I don't think that one is a security risk.