The following reply was made to PR mod_proxy/1326; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Apache bugs database <[EMAIL PROTECTED]> Cc: Subject: Re: mod_proxy/1326: HTTPS - Cannot Connect! (PR#1024, PR#1105) (fwd) Date: Wed, 29 Oct 1997 09:07:15 -0700 (MST) ---------- Forwarded message ---------- Date: Wed, 29 Oct 1997 09:49:06 +0100 From: Rainer Scherg RTC <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: mod_proxy/1326: HTTPS - Cannot Connect! (PR#1024, PR#1105) > 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. Yes, I've tried this first... Playing with "ProxyRemote" and "https" was a result due to the connect problem. > > 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 *" ? Yes, I've tried this... Connecting directly to our firewall (the remote proxy - it's a Netscape Enterprise Server) works fine for the https-requests. > > 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. I'll try... cu and tnx for help -- Rainer -------------------------------------------------------------------- Rainer Scherg, Abt. RTC, Mannesmann Rexroth AG e-Mail: [EMAIL PROTECTED], Tel/Fax: +49-9352-18-1510 /-1500
