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



The CGI app has to be running under some Apache instance. Setup SSL on
the Apache Instance and make everything going over port 8014 SSL

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas Handy
Sent: Monday, June 18, 2007 2:40 PM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Using SSL for CGIDEV2 requests

Short version: How can I use SSL for my XML transfers using CGIDEV2
service
programs?

Longer version:

I have setup CGIDEV2 listening on its default config of port 8014, and
have
written a couple of CGI programs to return some XML result sets. The
XML
requests will be coming from a single source, namely ASP scripts running
on
an off-site web host provider. That is all up and running just fine in
a
test environment.

Now what I'd like to do is enable encryption on the XML data flowing
between
to the web host provider before we put this in production. I don't
think I
can get the web provider to install a VPN client as a tunnel, so I
figure we
should be able to use SSL on the traffic. It doesn't appear to be as
easy
as just using HTTPS://myip.com:8014 in lieu of HTTP as the protocol
prefix.

How do I configure stuff so that the CGI requests will run via HTTPS?
If it
matters, they do not also need the regular default Apache instance
listening
on port 80 or generic HTTPS on port 443, so if necessary, I can use port
443
for the traffic.

Doug

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.