joeyjgarcia Posted September 5, 2006 Posted September 5, 2006 I got this email a while back from the USPS website regarding my account with them. Following is our information regarding the SSL Implementation for WebTools APIs. If you wish to continue using the APIs listed below, you must alter your code by September 30, 2006. You will be required to communicate via https://, instead of http://, for a total of 46 USPS Web Tools APIs. This change will also require you to change the Web Tools server called from production.shippingapis.com to secure.shippingapis.com. I tried to just change the URL and got this error. fsockopen(): unable to connect to secure.shippingapis.com I've request help for this before and someone told me that this topic is well documented but didn't provide me a URL, I searched for it and went through many page before giving up. Can someone please tell me what it required to make this change? thank you
jasonabc Posted September 5, 2006 Posted September 5, 2006 Ignore the email - the list of API's affected does not include the one OSC uses. Jason My Contributions: Paypal Payflow PRO | Rollover Category Images | Authorize.net Invoice Number Fix
joeyjgarcia Posted September 7, 2006 Author Posted September 7, 2006 Ignore the email - the list of API's affected does not include the one OSC uses. Are you sure? Is anyone else ignoring it? Did anyone else get this to work?
jasonabc Posted September 7, 2006 Posted September 7, 2006 Are you sure? Yes. I spoke with USPS a few months ago about this after a client of mine got the same email you did. They confirmed the rate calculator that the OSC USPS module uses is not on the list of affected API's. You can ignore the email. Jason My Contributions: Paypal Payflow PRO | Rollover Category Images | Authorize.net Invoice Number Fix
FixItPete Posted September 11, 2006 Posted September 11, 2006 Yes. I spoke with USPS a few months ago about this after a client of mine got the same email you did. They confirmed the rate calculator that the OSC USPS module uses is not on the list of affected API's. You can ignore the email. I too have called and verified that we need to do nothing. The API we use is to get quotes. It is not on the list. We're all good. :) Pete I find the fun in everything.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.