After at least eight years of running the same code twice a month, this week I got a error message from Google Maps API that reads:

"The date in the certificate is invalid or has expired"

What is strange, when I enter the URL request into Chrome address with maps Key the response comes back without any problem. Also verified that Maps dashboard still shows the Key and although it does not have an expired date, it also does not say it is active... google does a poor job if reporting the status of the key and shows that is is still in the account.

My question, when I try to debug HttpGetEx which is called by HttpGet, I can't see the source code (even after deleting all the FXP files) to step through the function thinking maybe I can learn something about the problem.

Any clues where to go looking for issues? Also opened a thread on Maps forum and waiting for a reply.

What OS?

Could be a TLS1.2 issue if you're on an old version of Windows that doesn't automatically support TLS 1.2.

Going to Google Maps and using the API are not the same thing - so different servers. Maybe an old server that Google no longer uses and the cert is actually bad by now?

+++ Rick ---

The server is Win 2003, I have not spent any more time on trying to find the answer after reading your reply. I will assume this was the problem. Thanks

If it's server 2003 it's almost certainly the TLS 1.2 issue. I don't think TLS 1.2 is supported on Server 2003 at all through Microsoft APIs.

Take another look at my post from a long while back on TLS 1.2 usage in Web Connection and West Wind and FoxPro in general:

Web Connection and TLS 1.2 Support

Looking at this old post, it says that Windows XP, Vista and Server 2003 don't have Windows support for TLS 1.2 through the Windows APIs. So look like out of luck on those platforms.

+++ Rick ---