Re: [BULK] Re: HTTPAPI sending a certificate.

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hello,

> Below is a copy and paste from the error log that I originally posted.
> SetError() #43: CommSSL_Read:  time-out!

This message is expected and normal.  It is waiting for a 100 header, 
which is optional.  So it waits for a fraction of a second, and if it's 
not received, it times out and continues without it.  It's completely 
normal to get this time-out message and does not indicate any sort of 
failure.

Regarding your other message...  I apologize for thinking you didn't 
understand the procedure.  But, you did not tell me that you tried to 
import it into the DCM, or that you spoke to IBM about it.  You simply 
asked me if you could do https_init('/path/to/cert') and I did not know 
about the other stuff you did.

The debug file you posted only shows an error with parsing XML (and the 
error is valid -- the XML they sent was not legal XML) I can only 
respond to what I understand and know about your situation.

So, many apologies if what I said was incorrect.

Currently, it sounds like the issue is due to an expired (not invalid, 
expired!) certificate.  The bank is expecting you to send an expired 
certificate in order to communicate with them, and when asked to solve 
the problem they tell you "it works for us because we can kludge it in 
PHP or Java".  Unfortunately, the DCM won't accept an expired 
certificate, so you're out of luck.

If you can get things working with PHP or Java, etc, then I'd suggest 
going that route.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------