Re: I need the SSL version to be backward-compatible with programs expecting the non-SSL version.

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

hi James,

The two signatures are not compatible.  You can't put one in a *PRV 
block and one in a *CURRENT block, that won't work, because they are not 
compatible.

1) Please put the source code back the way it was.  Keeping an invalid 
signature in HTTPAPI is something I cannot support.

2) Run the INSTALL program, and specify Y for the SSL support.

3) re-bind any existing programs (calling UPDPGM or UPDSRVPGM should 
suffice)




On 12/27/2011 8:03 PM, James Lampert wrote:
> We already have programs that depend on the non-SSL version of
> HTTPAPIR4, while the new programs need the SSL version.
>
> Toward this end, and following the "Binder Language" section of the ILE
> Concepts book, I tried adding the STRPGMEXP block from the HTTPAPI1
> member to the HTTPAPI2 member, as a *PRV STRPGMEXP block; I recompiled,
> and when the program expecting the non-SSL version tried to use it, it
> got an MCH3601 at a call to "http_url_get_raw."
>
> Any clue what could have gone wrong?
>
> --
> JHHL
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>

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