Re: HTTPAPI failing at V7R3

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Peter,

This error means that HTTPAPI sent a connect request without any errors, 
but didn't get a reply.

It almost always (90% of the time) means that a firewall is blocking 
access.  Occasionally (8-9% of the time) it means there's a mistake in 
routing.

-SK




On 9/18/2017 7:16 PM, Peter Connell wrote:
> Just upgraded to V7R3 and all requests via HTTPAPI are timing out with -
>
> http_url_get(): entered
> http_persist_open(): entered
> http_long_ParseURL(): entered
> DNS resolver retrans: 2
> DNS resolver retry  : 2
> DNS resolver options: x'00000136'
> DNS default domain: corp.bayadv
> DNS server found: 10.9.64.104
> DNS server found: 10.90.100.20
> DNS server found: 10.1.77.4
> Nagle's algorithm (TCP_NODELAY) disabled.
> SetError() #7: Timeout occurred while trying to connect to server!
>
> Any clues please?
>
> Regards, Peter
> ############################################################## This correspondence is for the named person's use only. It may contain confidential or legally privileged information, or both. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of Equifax. If you need assistance, please contact Equifax :- Australia www.equifax.com.au/contact New Zealand www.equifax.co.nz/contact ##############################################################