Date: 28 Oct 1997 14:44:24 -0000
Message-ID: <19971028144424.19476.qmail@hyperreal.org>
To: apache-bugdb@apache.org, marc@apache.org, rainer.scherg@rexroth.de
From: marc@hyperreal.org
Subject: Re: mod_proxy/1326: HTTPS - Cannot Connect! (PR#1024, PR#1105)
Sender: apache-bugdb-owner@apache.org
Precedence: bulk

Synopsis: HTTPS - Cannot Connect! (PR#1024, PR#1105)

State-Changed-From-To: open-analyzed
State-Changed-By: marc
State-Changed-When: Tue Oct 28 06:44:24 PST 1997
State-Changed-Why:
The base Apache does not have SSL built in so it can not
talk to a server over a SSL connection.  That means
all connections to port 443 are doomed to failure.

The normal way to handle this is to use the CONNECT
method, which is automatically used for https requests
and which is sent to the normal webserver port.

Does proxy1.mannesmann.de support CONNECT?  If not, it
will never work and is not supposed to.  If it does, have
you tried it with just a "ProxyRemote *" ?

If this doesn't help, recompile Apache with "-g" added to
the EXTRA_CFLAGS for debugging info, add a CoreDumpDirectory
directive to put the core dumps somewhere writable, then
get a core dump and run gbd on it to see where it is dumping.