Apache2 SSL problem

External Since: Dec 22, 2004 Posts: 3

Hello,

I have spent the past few weeks trying to get SSL working on Suse
Enterprise server 9.1 with Apache 2. I have followed several guides
all of which were pretty similar give or take an item or two. I have
made sure that /etc/sysconfig/apache2 has ssl listed under
APACHE_MODULES and that APACHE_SERVER_FLAGS="-D SSL"

I have setup one virtual host as minimally as possible using the
template included in the installation and generated my certificate as
instructed.

When I run httpd2 -D SSL -S it tells my Syntax OK. When trying to
access the server via https I see the following in the access_log

192.168.42.230 - - [22/Dec/2004:07:41:06 -0800] "\x80g\x01\x03" 200
709 "-" "-"
192.168.42.230 - - [22/Dec/2004:07:41:09 -0800] "\x80g\x01\x03" 200
709 "-" "-"

With debugging on I see the following in the error.log

[Wed Dec 22 07:49:05 2004] [info] Shared memory session cache
initialised
[Wed Dec 22 07:49:05 2004] [info] Init: Initializing (virtual) servers
for SSL
[Wed Dec 22 07:49:05 2004] [warn] Init: (192.168.42.89:443) You
configured HTTP(80) on the standard HTTPS(443) port!
[Wed Dec 22 07:49:05 2004] [info] Server: Apache/2.0.49, Interface:
mod_ssl/2.0.49, Library: OpenSSL/0.9.7d
[Wed Dec 22 07:49:06 2004] [notice] mod_python: Creating 32 session
mutexes based on 150 max processes and 0 max threads.
[Wed Dec 22 07:49:06 2004] [notice] Apache/2.0.49 (Linux/SuSE)
configured -- resuming normal operations
[Wed Dec 22 07:49:06 2004] [info] Server built: Nov 9 2004 22:42:30
[Wed Dec 22 07:49:06 2004] [debug] prefork.c(955): AcceptMutex:
sysvsem (default: sysvsem)

I have gone through all of the conf files, but can not see where I
have configured HTTP(80) on the standard HTTPS(443) port.

Anyone have any ideas?

External Since: Nov 03, 2003 Posts: 2907

On 2004-12-22, brlaas <no RemoveThis @no.net> wrote:
> I have gone through all of the conf files, but can not see where I
> have configured HTTP(80) on the standard HTTPS(443) port.

When Apache is configured for SSL usually you end up with something
like

Listen 80
<IfDefine SSL>
Listen 443
</IfDefine>

Then in the VirtualHost section:

<IfDefine SSL>
<VirtualHost *:443>
.....
</VirtualHost>
</IfDefine>

This makes apache listen to port 443 _only_ when SSL is enabled and on
port 80 for 'normal' http. I suppose that in your case you miss the
'443' part, so you're running https on port 80. Now, normally browsers
when instructed to use https switch automatically to port 443. This
keeps the two way separated. If you want to run https only, change your
'listen' directive to listen only on port 443.

Davide

--
We are at one with our work. If you disturb our work, our foot will be at
one with your ass.
-- J. Gostin on alt.sysadmin.recovery