West Wind Client Tools
wwHTTP.httpGet() fails with
Gravatar is a globally recognized avatar based on your email address. wwHTTP.httpGet() fails with
  Dan Lauer
  All
  Feb 24, 2017 @ 11:08am

I'm hitting the same endpoint from two different networks using wwHTTP with identical credentials, headers, etc., and getting different results. Everything works great from my network, but from the customer's network the httpGet() fails with .cErrorMsg = "The connection with the server was reset". If I do the same call with the Chrome Advanced REST Client app at the customer site, it works fine. I replace the copy of wwIPStuff.dll at the customer site, no change.

Our application has been installed at this customer site for several years and this problem started two days ago.

I've tried other calls to other endpoints using wwHTTP at the customer's site and they work. Not sure what to try next, but I'll keep hammering away.

Ideas?

UPDATE: The problem endpoint has been the BigCommerce API. I decided to try hitting a different BigCommerce store's API endpoint from the customer's site. Works. I'm going to start drinking.

Gravatar is a globally recognized avatar based on your email address. re: wwHTTP.httpGet() fails with
  Rick Strahl
  Dan Lauer
  Feb 24, 2017 @ 02:15pm

Bad certificate perhaps? TLS version issue?

Connection Reset errors are usually caused by low level connection problems - proxy servers, SSL problems. For example, if you run with Fiddler enabled (which is effectively a proxy) it's not uncommon to see connection errors.

+++ Rick ---

Gravatar is a globally recognized avatar based on your email address. re: wwHTTP.httpGet() fails with
  Dan Lauer
  Rick Strahl
  Feb 24, 2017 @ 04:32pm

If it were a certificate issue, would I not see this from anywhere? I can hit this BigCommerce store API from anywhere but this customer's system.

Any suggestions on how to research/resolve a TLS version issue?

Gravatar is a globally recognized avatar based on your email address. re: wwHTTP.httpGet() fails with
  Dan Lauer
  Rick Strahl
  Feb 24, 2017 @ 04:49pm

It was the TLS version. We found where to configure this in server 2008 R2, enabled 1.2 and it's working now. Thanks for the tip!

© 1996-2017