Jim,No worries, here... HTTPAPI always lets you choose whether you are making an SSL or non-SSL request. It's very simple, if you supply a URL starting with http:// it is not SSL. If you use https://, then it is SSL -- just as it would be in a browser.
The question about whether to compile with/without SSL support is probably obsolete at this point. It was originally there for people running releases prior to V4R5, which didn't have the OS support that HTTPAPI needed for SSL, so if you compiled with SSL back then, the compile would fail. Probably everyone today should be compiling "with" SSL support, there's no disadvantage to that anymore.
-SK On 12/5/2015 8:03 PM, Jim Franz wrote:
Just installed LIBHTTP, and selected the option to not support SSL.
However that's a discussion we have not had. Expecting some to be with
SSL (outside the network perimeter, others are strictly internal
between servers).
Will the SSL version support non SSL connections? What is the best way
to deal with this issue?
Are there any other initial setup issues that require better planning?
We currently support direct SQL calls from Win servers, some stored
procedures, and ftp batch processing.
Now looking at web services with connection to DB2 (unix) servers that
will host a large group of apps we have to work with in real time.
Trans will flow in both directions.
Jim Franz
----------------------------------------------------------------------- This is the FTPAPI mailing list. To unsubscribe, please go to: http://www.scottklement.com/mailman/listinfo/ftpapi -----------------------------------------------------------------------