Re: New apache-ssl problem

* Christopher Swingley <[EMAIL PROTECTED]> [2002-Jun-20 14:04 AKDT]: > I just upgraded apache, apache-common, and apache-ssl to the 1.3.26 > versions recently uploaded to http.us.debian.org. The standard apache > seems to be working fine, but the SSL version isn't doing SSL. It's > running, but n

New apache-ssl problem

I just upgraded apache, apache-common, and apache-ssl to the 1.3.26 versions recently uploaded to http.us.debian.org. The standard apache seems to be working fine, but the SSL version isn't doing SSL. It's running, but not encrypted, so Mozilla won't get any data and I can telnet to the apache-ss

Re: Apache-SSL problem....

What else would you want to listen on port 80? apache-ssl typically listens on port 80 for normal http requests, and port 443 for https requests (though these can be changed). If you don't want it listening on port 80, change the line in httpd.conf that says "Listen ...". You can set it up only t

Apache-SSL problem....

I'm having trouble getting Apache-SSL to NOT bind to every address on the box. I have removed the BindAddress * configuration line, and replaced it with "BindAddress AAA.BBB.CCC.XXX", but this changed nothing. In a nestat -a I still see a "*:www LISTENING" and I am unable to launch any other pro

Apache SSL problem

I installed hamm's Apache-SSL and can connect to it from the server (http[s]://localhost/) w/o problems. But if I try to connect from a different computer all I see is an alert with "Document contains no data". What's this?