I just realised that what's probably happening is that Apache isn't
listening on 443 and the secure requests are going straight to 4D
which is serving them as before.
This actually isn't a bad solution for us since only the checkout
page is secure and forms a very small part of the traffic.
Is anyone aware of this being a problematic configuration ?
Peter
On 28 Jan 2008, at 13:49, Steve Alex wrote:
Don't know if this is the right way, but we set up virtual hosts in
the ssl.conf that listens on port 443
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
