RE: updating libhttp from 1.24 to 1.29?

[Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>]

I have only used expat within my LIBHTTP. I could be wrong but I don't think the expat code base changed since 1.24. You can check in the changelog for notes about that (I don't have access to the IBMi tonight).

Since it is by default compiled into LIBHTTP and used with LIBHTTP, I would delete the LIBEXPAT and start compililng and using it in LIBHTTP. Do you think someone might have customized expat? That would be a reason to keep it separate.
________________________________________
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Koester, Michael [mkoester@xxxxxxxxxxxxx]
Sent: Friday, January 08, 2016 4:49 PM
To: HTTPAPI and FTPAPI Projects
Subject: RE: updating libhttp from 1.24 to 1.29?

Thanks Mike.
I think we must have included an ExPat option in with our original install -- we have LIBEXPAT.  Would you advise updating that as well?

Michael

> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-
> bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Krebs
> Sent: Friday, January 08, 2016 5:28 PM
> To: HTTPAPI and FTPAPI Projects
> Subject: RE: updating libhttp from 1.24 to 1.29?
>
> As far as SSL, that is the message if compiled without TLS (SSL) support.
>
> If you have custom programs in LIBHTTP, you should move the source to
> another library.
>
> Then follow the install instructions and put it right on top of what you
> already have.
> If your custom source is gone, copy back and recompile.
> All should be good.
>
> 1.24 to 1.29 is highly compatible. Mostly fixes in the upgrades.
>
> Your existing programs in other libraries will pick up the service
> programs in LIBHTTP and should run just fine. If not, a quick recompile
> should fix. You can test by installing in a different library if you want.
>
> -----Original Message-----
> From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-
> bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Koester, Michael
> Sent: Friday, January 8, 2016 3:04 PM
> To: ftpapi@xxxxxxxxxxxxxxxxxxxxxx
> Subject: updating libhttp from 1.24 to 1.29?
>
> A few years back I installed v1.24, and it has been very useful in a
> number of applications.  Now I'm trying to get another application up and
> running, but I suspect I need the SSL capability that may not have been
> selected in that install.  I'm getting an error, "Only the http protocol
> is available!", which suggests I need to reinstall with the SSL capability
> selected?
> Is there a way to confirm that the SSL was not installed? Or does that
> error message happen only for that reason?
>
> My applications use the objects straight out of LIBHTTP, and we run iOS
> 7.1.
> Is it likely that I can re-install with v1.29 and the SSL option, without
> hurting the current applications?
> What are the steps to follow in that kind of update?
>
> Thanks,
> Michael Koester
> Programmer/Analyst
> DataEast - Granite State Communications
> -----------------------------------------------------------------------
> 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
> -----------------------------------------------------------------------

-----------------------------------------------------------------------
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
-----------------------------------------------------------------------