That's exactly what I did. Unfortunately, the server times out when accessed.
via the
www. So, let me emphasize a couple of points:
1) The HTTP server and the HTTPS server reside on the same Linux server
with the HTTPS being a virtual host run on Apache 2.0
2) They share a common interface. The server is not dual homed and
only has 1 NIC. Nevertheless the HTTPS server requires its own separate
interface. To accomplish this I have set up an aliased ip address as follows:
## ===================================================
# set up an aliased ip address for the secure.pctechnirvana.com
# SSL transaction server
/sbin/ifconfig eth0:0 192.168.1.5
/sbin/route add -host 192.168.1.5 dev eth0:0
## ===================================================
Here eth0 and eth0:0 actually point to the same device. This allows me to
fool the OS into thinking that there are two NICs. This allows me to run the
HTTP server on eth0 @192.168.1.4:80 and the HTTPS server on eth0:0
@192.168.1.5:443. Actually, both servers are sharing a single device.
This may not be relevant but I thought I'd mention it just in case.
My instinct tells me that I may be getting blocked by a previous rule from
the iptables. I'll strip the script down to the bare essentials and see if I
can get it to work by adding stuff back in incrementally.
If that fails then I'll post my script later. Will let you know how it turns out
Thanks CMD