Closed stucka closed 1 year ago
Trying to use the more-up-to-date certifi fails. Looks like it's Arizona's fault.
Certificate chain 0 s:C = US, ST = Arizona, L = Phoenix, O = Arizona Department of Economic Security, CN = azjobconnection.gov i:C = US, O = DigiCert Inc, CN = DigiCert Global G2 TLS RSA SHA256 2020 CA1 1 s:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert High Assurance EV Root CA ...
SSL handshake has read 3519 bytes and written 475 bytes Verification error: unable to verify the first certificate
Workaround built: https://github.com/biglocalnews/warn-scraper/compare/1.2.36...1.2.37
Have messaged Arizona to let them know of certificate problem. If they get it fixed, the verify=False line in az.py can get removed, or set to true.
Arizona installed a new SSL certificate on Aug. 11, and Arizona's scraper started throwing certificate errors on ... Aug. 11.
Maybe this gets itself cleaned up, we need to look for better certificate upgrades like certifi, or we just force Arizona's scraper to use verify = False in the short or long term.