Depending on what you're running inside AOLserver, and your reason for needing SSL, this may not work the way you expect. Since you're launching 2 distinct nsd processes, one bound to each of the http and https ports, any state that is held in the http server won't be available if a user starts accessing the https part of your site and vice-versa. Essentially you're running a server cluster, with all the attendant synchronisation issues...
This may not be a problem, depending on the application you're running in AOLserver, but is certainly worth being aware of...
cheers
Russell
On 10/12/2003, at 1:34 PM, Manish Mukherjee wrote:
okay, a reply to my own reply. since i had just figured out the workaround, it didn't occur to me that i would be easier to do the following:
instead of:
/usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:80 -b 216.167.89.78:443 AND /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443 -b 216.167.89.78:80
do this:
/usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:80 AND /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443
the net result after both is the same, the second is just a little neater.
mkm
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
