[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: updating libhttp from 1.24 to 1.29?



   Scott

   So once you install this, will you have to recompile the web service
   programs that use the copy books etc etc
   From httpapi?
   [1]Sent from Yahoo Mail for iPhone

   On Wednesday, January 13, 2016, 5:41 PM, Scott Klement
   <sk@xxxxxxxxxxxxxxxx> wrote:

   Michael,
   After loading HTTPAPI, you need to run the install program that comes
   with it.  You can do this by putting the library at the top of your
   libl
   and then CALL INSTALL
   On one of the screens in the installer, it asks "Would you like to
   build
   HTTPAPI with SSL support?"  You must answer this question with Y.
   Compiling HTTPAPI with this set to N is the only way you will get the
   "Only the http protocol is available" message (aside from modifying the
   source of HTTPAPI).    If you start getting a similar message saying
   "Only the http and https protocols are available" that is a different
   story.
   -SK
   On 1/13/2016 4:02 PM, Koester, Michael wrote:
   > Thanks for the assist, Mr. Krebs.
   > But I still getting the error, "Only the http protocol is available!"
   >
   > Since I am not positive that we don't have any customization in
   LIBHTTP, I had SysAdmin bring in the v1.29 in, specifying the SSL
   support (but not a new ExPat).  Had him set target lib to "LIBHTTP2",
   leaving LIBHTTP intact.  All the new objects were created in LIBHTTP2
   as well.
   > To test:
   >     I set LIBHTTP2 ahead of LIBHTTP in my library list.
   >     I re-created my service program with BNDDIR(LIBHTTP2/HTTPAPI).
   >     I recompiled my test program.
   >     I called my test program and stepped through with the SEP
   debugger.
   >     The call to http_url_post_xml returned rc = -1.
   >     The call to http_error() returned "Only the http protocol is
   available!".
   >
   > The call to http_url_post_xml looks like this:
   >    rc = http_url_post_xml(NeoNovaURL
   >                        : %addr(postData : *DATA)
   >                        : %len(postData)
   >                        : %paddr(StartOfElement)
   >                        : %paddr(EndOfElement)
   >                        : *NULL );
   >
   > NeoNovaURL is: '[2]https://xml.NeoNova.net/NNSAPI.fcgi'
   >
   > PostData is: '<?xml version="1.0"?>
   >
   <authenticate><user>xxxxxx</user><pass>xxxxxxx</pass><domain>mygsc.com<
   /domain></authenticate>
   > <get_userinfo><user><userid>bob</userid></user></get_userinfo>'
   >
   > [I inserted line breaks here, and login credentials are masked with
   xxxxxx]
   >
   > In our test environment, I can hit the
   [3]http://sandbox-api.neonova.net/NNSAPI.fcgi site from the same
   program with no problem, and get expected results.
   >
   > I can use the HttpRequester browser plugin, send the same parameters
   to the production (https/...) site, and get expected results.
   >
   >
   > So where do I look to diagnose the cause?
   >
   > I'll be here for another hour today, then back at 7:30 AM EST
   tomorrow.
   >
   > Michael Koester
   >
   >> -----Original Message-----
   >> From: [4]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-
   >> [5]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: [6]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-
   >> [7]bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Koester, Michael
   >> Sent: Friday, January 8, 2016 3:04 PM
   >> To: [8]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:
   >> [9]http://www.scottklement.com/mailman/listinfo/ftpapi
   >>
   -----------------------------------------------------------------------
   >>
   -----------------------------------------------------------------------
   >> This is the FTPAPI mailing list.  To unsubscribe, please go to:
   >> [10]http://www.scottklement.com/mailman/listinfo/ftpapi
   >>
   -----------------------------------------------------------------------
   >
   -----------------------------------------------------------------------
   > This is the FTPAPI mailing list.  To unsubscribe, please go to:
   > [11]http://www.scottklement.com/mailman/listinfo/ftpapi
   >
   -----------------------------------------------------------------------
   >
   -----------------------------------------------------------------------
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   [12]http://www.scottklement.com/mailman/listinfo/ftpapi
   -----------------------------------------------------------------------

References

   Visible links
   1. https://yho.com/footer0
   2. https://xml.NeoNova.net/NNSAPI.fcgi'
   3. http://sandbox-api.neonova.net/NNSAPI.fcgi
   4. javascript:return
   5. javascript:return
   6. javascript:return
   7. javascript:return
   8. javascript:return
   9. http://www.scottklement.com/mailman/listinfo/ftpapi
  10. http://www.scottklement.com/mailman/listinfo/ftpapi
  11. http://www.scottklement.com/mailman/listinfo/ftpapi
  12. http://www.scottklement.com/mailman/listinfo/ftpapi

   Hidden links:
  13. https://xml.NeoNova.net/NNSAPI.fcgi'
  14. http://sandbox-api.neonova.net/NNSAPI.fcgi
  15. http://www.scottklement.com/mailman/listinfo/ftpapi
  16. http://www.scottklement.com/mailman/listinfo/ftpapi
  17. http://www.scottklement.com/mailman/listinfo/ftpapi
  18. 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
-----------------------------------------------------------------------