You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crawl of a site supporting only TLS 1.2 was failing. Modifying the constructors of the PageRequester assigning the default security protocol resolves the problem for us. This may not be the best home for assigning the SecurityProtocol setting. Also does not future proof for TLS 1.3.
Thanks for reporting this. I agree that Abot may not be the best initializer of this setting. I will leave this issue open so others have a workaround.
Took me a while to find it though. Adding the error text I was getting: "Could not create SSL/TLS secure channel" (just so Google indexes it and brings more people to the workaround.)
sjdirect
changed the title
TLS 1.2 Support
Abot AbotX TLS 1.2 Support, Could not create SSL/TLS secure channel
Mar 13, 2019
The crawl of a site supporting only TLS 1.2 was failing. Modifying the constructors of the PageRequester assigning the default security protocol resolves the problem for us. This may not be the best home for assigning the SecurityProtocol setting. Also does not future proof for TLS 1.3.
The text was updated successfully, but these errors were encountered: