|
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Oftraffic to
Douglas Handy
Sent: Monday, April 24, 2017 7:22 PM
To: RPG programming on the IBM i / System i
Subject: Providing web services using HTTPS
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%2
0Services%20on%20IBM%20i.pdf
I can get everything to work when using http:// but I'd like the
happen of TLS 1.x instead of plain text. The web service runs on itsown port,
not 80 or 443. This works:than
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
the listen port of xxxx.for me
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
to do my own encrypt / decrypt (and EBDIC conversion) and pass binarydata
instead of trying to piggy back off https support.of the
But is there a way to have the web service traffic just take advantage
HTTPS support?(RPG400-L)
--
This is the RPG programming on the IBM i (AS/400 and iSeries)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx Tosubscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.