Getting false alarm on URL response probe due to " SSL Connect error (35) ". However when test is done on profile it is fetching response successfully but giving alarm intermittently though application is up and running .
This issue seen more frequently when url_response probe is monitoring mix of TLS 1.2 and SSL v3 target urls
1.Deploy the latest GA build of the url response probe (4.46) or higher on the problematic server where Connect error 35 gets reproduced quite frequently 2.Add a key "retry" with value as 15 under the problematic profile which produces 35 error
The url_response probe is already doing the retry based on the configured value so it is not a good idea to hard code this value because this value depends on the amount of redirection i.e. for some URL there might not exist any redirection but for some other URL there might be 7-8 or even more level of redirection, so the retry interval could not be generalized and it has to be configurable based on the configured URL.