Closed AndySchmitt closed 5 years ago
Thanks for indicating the problem.
I will try to fix it this weekend. However, security is complicated, so I will have to research first what combinations of values creates the least problems. It might take sometimes.
I do not think I will fix this issue, but I have added a note about it in the README.
I think that this is the best way because any change on the property ServicePointManager.SecurityProtocol
might affect also requests made by other parts of the code (see documentation). This will be unexpected and might cause weird bugs to some user of the library.
SmartReader does not specify Security Protocols after the creation of HttpClient, this causes a 502 bad gateway response from server.
I solved this problem specifying the SecurityProtocol after the creation of HttpClient:
Here is a test case: https://girosa.com.br/politica/empresa-que-presta-servicos-em-osasco-integra-consorcio-do-lixo-investigado-pela-pf