Hi All,

I'd like some information on this from those of you who have it running:

Q: When you install apache and apache-ssl in Debian; There are two configs made:

/etc/apache
/etc/apache-ssl

How does this arrangement work with regards to handling incoming requests?

* Does one config only listen on ssl ports?
* How does it handle the session between the two instances?
* If a website has a non-ssl initial page does it have to be split between the two instances?

I'm contemplating creating a CVS accessible location where I can do Thunderbird Calendar Syncing and I'm trying to figure out how to get this to co-exist with the current in-place and running apache server... Off to google this some more but your 'informed' input is most welcome!

This is more an apache question than it is a Debian question ( However, it is true that the Debian branch release may have done something goofy, wouldn't be the first, won't be the last )

You'll set up your SSL stuff in your httpd.conf file. When you start up apache, you'll start it up with the -DSSL option, which is usually done via apachectl startssl

Thanks for the response...

Yup. got that. However, there are two config dirs that the installs look at. One in /etc/apache and the other is /etc/apache-ssl. I use vhosts files and I am wondering if I have to symlink the site file from the /etc/apache/conf.d/ location into the /etc/apache-ssl/conf.d/ dir.

Hmmm... I'll have to check this out. I didn't look at the apache-ssl init script... Thanks for the nudge!

Yeah, sorry, don't know about the seperate directory thing. I usually roll my own apache, dont' use default install, etc. All my vhost stuff I set up in the httpd.conf file. Hopefully, you can either figure it out or someone else can chime in.

s'alright... 'preciate the effort!