×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I am setting up a web service following the methods described by Scott
Klement in his presentation at:
http://www.scottklement.com/presentations/Providing%20RPG%20Web%20Services%20on%20IBM%20i.pdf
I can get everything to work when using http:// but I'd like the traffic to
happen of TLS 1.x instead of plain text. The web service runs on its own
port, not 80 or 443. This works:
http://myserver.com:xxxx/yada/yada/yada
This does not work:
https://myserver.com:xxxx/yada/yada/yada
Nothing in the server instance httpd.conf seems to be related, other than
the listen port of xxxx.
I also can't find discussion of this in the XMLHttpRequest docs at:
https://xhr.spec.whatwg.org/
I can control both the client and server side, so one option would be for
me to do my own encrypt / decrypt (and EBDIC conversion) and pass binary
data instead of trying to piggy back off https support.
But is there a way to have the web service traffic just take advantage of
the HTTPS support?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
