Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 87186 invoked by uid 500); 24 Apr 2002 03:07:13 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 87175 invoked from network); 24 Apr 2002 03:07:13 -0000 Received: from mtiwmhc21.worldnet.att.net (204.127.131.46) by daedalus.apache.org with SMTP; 24 Apr 2002 03:07:13 -0000 Received: from ScottIsaar ([12.76.87.159]) by mtiwmhc21.worldnet.att.net (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020424030721.WOQX24238.mtiwmhc21.worldnet.att.net@ScottIsaar> for ; Wed, 24 Apr 2002 03:07:21 +0000 From: "Scott Seidl" To: Subject: RE: FW: Apache 1.3.24 & mod_ssl Date: Tue, 23 Apr 2002 22:07:20 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal In-Reply-To: <1019567294.18504.1457.camel@linux> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I tried using the ip of 127.0.0.1 which is the IP that is given by my Windows 2000 box for my Linux box and received no result for either http or https. I then tried the assigned by my ISP (yes I am still on Dial Up), which at the time was 192.168.0.171. The http request worked fine, but again the https request did not. I tried both the https and http://192.168.0.171:443 and neither ssl request worked. To me it appears that apache is not listening for the https request on port 443, even though it is in my httpd.conf file. Below is a section of the http.conf file, appearing in Section 2.: # # Port: The port to which the standalone server listens. For # ports < 1023, you will need httpd to be run as root initially. # Port 80 ## ## SSL Support ## ## When we also provide SSL we have to listen to the ## standard HTTP port (see above) and to the HTTPS port ## Listen 80 Listen 443 Thanks again for the past and future help. Scott -----Original Message----- From: Lee Fellows [mailto:lfellows@4lane.com] Sent: Tuesday, April 23, 2002 8:08 AM To: users@httpd.apache.org Subject: RE: FW: Apache 1.3.24 & mod_ssl On Tue, 2002-04-23 at 08:49, Scott Seidl wrote: [ ...snip... ] > > When I try to access https://isaar... from the windows box, there are no > entries that are the access_log or error_log showing that Apache even > received the request. I can access non-SSL from my windows box with > http://isaar... > This is interesting: it sounds like the browser is getting different IP addresses for the same domain when it does its dns resolution... > I don't believe I tried using the ip address of the Linux box, so that is > something I will try. Let us know what you get with this test. > > Please note, 99% of the time, I access my Linux box through SSL, so > everything need to be configured from the command line. Doesn't everyone. :) My workstation is a linux box, but the servers I manage are mostly various Sun boxes running Solaris 8. I use SSL to access them and prefer the command-line to GUIs. I realize not everyone does, but I find the command-line much easier to work with. > > Again, thanks for the help and future help. > > Scott --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org