Re: Providing web services using HTTPS

By default http:// uses port 80. Also https:// uses port 443 by default.

If you're using SSL on a different port, you'll need to specify the port:

https://service.org:4433



Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud
Provider!

On Mon, Apr 24, 2017 at 7:22 PM, Douglas Handy <dhandy@xxxxxxxxx> wrote:

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 is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, 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