|
Hello Scott and Michael, I'm having a very similar error since middle of May when using Amazon MWS. Sometimes it works and sometimes it doesn't. Only
Amazon MWS. Others work well. I'm still waiting for a reply of our network guy, whether he can see something more. Do you also use Amazon MWS Michael? I'm using HTTPAPI Ver 1.38 released 2017-10-09 NTLM Ver 1.4.0 released 2014-12-22 OS/400 Ver V7R3M0 My log looks like: [...] https_init(): entered QSSLPCL = *OPSYS SSL version 2 support disabled SSL version 3 support disabled Old interface to TLS version 1.0 support enabled TLS version 1.0 support enabled TLS version 1.1 support enabled TLS version 1.2 support enabled ------------------------------------------------------------------------------------- Dump of local-side certificate information: ------------------------------------------------------------------------------------- Nagle's algorithm (TCP_NODELAY) disabled. SNI hostname set to: mws.amazonservices.de (GSKit) Peer not recognized or badly formatted message received.
ssl_error(415): (GSKit) Peer not recognized or badly formatted message received.
SetError() #30: SSL Handshake: (GSKit) Peer not recognized or badly formatted message received.
http_close(): entered |
-- _______________________________________________ Ftpapi mailing list Ftpapi@xxxxxxxxxxxxxxxxxxxxxx http://scottklement.com/mailman/listinfo/ftpapi