You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Scott Seidl <ap...@worldnet.att.net> on 2002/04/21 19:07:44 UTC
FW: Apache 1.3.24 & mod_ssl
> I have just configured Apache 1.3.24 and mod_ssl. I can connect to the
> url thru normal http just fine, but when I try to use https or port 443, I
> get page cannot be displayed. I double check the httpd.conf file to
> ensure that it was listening to port 80 and 443 under the <IfDefine SSL>
> tag (see segment below).
>
> Is there anything else that I should check to find out why I can't reach
> the site with https?
>
> #
> # 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
> ##
> <IfDefine SSL>
> Listen 80
> Listen 443
> </IfDefine>
>
> Thanks
> Scott
>
> -----------------------------------------------------------
> Scott Seidl
> Secretary of the Isaar Trail Riders Snowmobile Club
> Seymour, Wisconsin
> ------------------------------------------------------------
> Email: secretary@isaartrailriders.com
> Web Address: www.isaartrailriders.com
>
>
Re: FW: Apache 1.3.24 & mod_ssl
Posted by "Jack L. Stone" <ja...@sage-one.net>.
At 09:14 AM 4.24.2002 +0200, Owen Boyle wrote:
>Scott Seidl wrote:
>>
>> 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.
>
>This isn't right. 127.0.0.1 on ALL systems (linux or windows) is a
>loopback address (localhost). i.e. it is an IP address which allows
>processes on the same machine to communicate. It can NEVER be used
>across a network.
>
>> 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.
>
>It seems that you are simply not listening to port 443. To check this do
>"# netstat -a | grep 443" and look for a process binding to 443.
>
>You are starting apache with SSL, I hope (i.e. apachectl startSSL or
>httpd -DSSL or something - you have to pass the environment variable
>"SSL" to apache if you use <IfDefine>).
>
>Rgds,
>
>Owen Boyle.
>
Or try this to see all ports listening:
# netstat -na | grep LIST
.... our website: http://www.sage-one.net/
Best regards,
Jack L. Stone
Server Admin
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Scott Seidl <ap...@worldnet.att.net>.
Doh, do I feel like an idiot right now. I had the Red Hat firewall set to
the highest level, so the request to port 443 was never making it through.
Thanks for all the ideas though.
Scott
-----Original Message-----
From: Lee Fellows [mailto:lfellows@4lane.com]
Sent: Thursday, April 25, 2002 6:57 AM
To: users@httpd.apache.org
Subject: RE: FW: Apache 1.3.24 & mod_ssl
Hi Scott,
Normally, apache would listen on all interfaces, but it appears to not
be the case in your situation. Something you may try is to specify
Listen 192.168.0.171:443 in the httpd.conf file and see if you can then
see the page. Another thought, is the IP address (192.168.0.171) a
static address, or does the box get this address sometime after
starting? Why I ask is because I do not believe apache would see
an interface added after it had been started.
What happens if you telnet to the 192.168.0.171 443?
On Wed, 2002-04-24 at 23:17, Scott Seidl wrote:
> Thanks for all the sugestions. I misunderstood exactly how the Windows
2000
> Gateway worked. Thanks for clearing it up a bit.
>
> As for the correct IP (found by running /sbin/ifconfig -a as suggested by
> Lee) it came up with the 192.168.0.171. Again, using this IP I can reach
> the introductory apache page through http but not https.
>
> When I run "netstat -na | grep LIST" as suggested by Jack, I get the
> following output:
> tcp 0 0 127.0.0.1:32768 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
> unix 2 [ ACC ] STREAM LISTENING 1203 /dev/gpmctl
> unix 2 [ ACC ] STREAM LISTENING 1381 /tmp/.X11-unix/X0
> unix 2 [ ACC ] STREAM LISTENING 1302
> /tmp/.font-unix/fs7100
> unix 2 [ ACC ] STREAM LISTENING 1280
> /var/lib/mysql/mysql.sock
>
> When I run "netstat -a | grep 443" as suggested by Owen, I get no ouput.
> When I remove the grep 443, I get the following output:
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 0 0 localhost.localdo:32768 *:* LISTEN
> tcp 0 0 *:32769 *:* LISTEN
> tcp 0 0 *:mysql *:* LISTEN
> tcp 0 0 *:sunrpc *:* LISTEN
> tcp 0 0 *:http *:* LISTEN
> tcp 0 0 *:x11 *:* LISTEN
> tcp 0 0 *:ftp *:* LISTEN
> tcp 0 0 *:ssh *:* LISTEN
> tcp 0 0 localhost.localdom:smtp *:* LISTEN
> tcp 0 0 *:https *:* LISTEN
> tcp 0 0 192.168.0.171:ssh 192.168.0.1:3294
> ESTABLISHED
>
> When you look at the output from both, there are entries for port 443 and
> https, both in a Listen state. To the untrained eye of mine, it appears
> that Apache is listening to port 443.
>
> Thanks all for the past and future help!!!!
>
> Scott
>
> -----Original Message-----
> From: Lee Fellows [mailto:lfellows@4lane.com]
> Sent: Wednesday, April 24, 2002 9:32 AM
> To: users@httpd.apache.org
> Subject: RE: FW: Apache 1.3.24 & mod_ssl
>
>
> Scott,
>
> 127.0.0.1 is localhost on any machine running an IP stack. Hence
> your Windows 2000 host is attempting to connect to itself, not the
> Linux box, if you issue an http://127.0.0.1/ or https://127.0.0.1/.
> Try running /sbin/ifconfig -a on your Linux host to see what network
> interfaces are defined. You should see something like eth0 with a
> defined IP address. Try using this one.
>
>
>
> On Tue, 2002-04-23 at 23:07, Scott Seidl wrote:
> > 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
> > ##
> > <IfDefine SSL>
> > Listen 80
> > Listen 443
> > </IfDefine>
> >
> > 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Lee Fellows <lf...@4lane.com>.
Hi Scott,
Normally, apache would listen on all interfaces, but it appears to not
be the case in your situation. Something you may try is to specify
Listen 192.168.0.171:443 in the httpd.conf file and see if you can then
see the page. Another thought, is the IP address (192.168.0.171) a
static address, or does the box get this address sometime after
starting? Why I ask is because I do not believe apache would see
an interface added after it had been started.
What happens if you telnet to the 192.168.0.171 443?
On Wed, 2002-04-24 at 23:17, Scott Seidl wrote:
> Thanks for all the sugestions. I misunderstood exactly how the Windows 2000
> Gateway worked. Thanks for clearing it up a bit.
>
> As for the correct IP (found by running /sbin/ifconfig -a as suggested by
> Lee) it came up with the 192.168.0.171. Again, using this IP I can reach
> the introductory apache page through http but not https.
>
> When I run "netstat -na | grep LIST" as suggested by Jack, I get the
> following output:
> tcp 0 0 127.0.0.1:32768 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
> tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
> tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
> unix 2 [ ACC ] STREAM LISTENING 1203 /dev/gpmctl
> unix 2 [ ACC ] STREAM LISTENING 1381 /tmp/.X11-unix/X0
> unix 2 [ ACC ] STREAM LISTENING 1302
> /tmp/.font-unix/fs7100
> unix 2 [ ACC ] STREAM LISTENING 1280
> /var/lib/mysql/mysql.sock
>
> When I run "netstat -a | grep 443" as suggested by Owen, I get no ouput.
> When I remove the grep 443, I get the following output:
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State
> tcp 0 0 localhost.localdo:32768 *:* LISTEN
> tcp 0 0 *:32769 *:* LISTEN
> tcp 0 0 *:mysql *:* LISTEN
> tcp 0 0 *:sunrpc *:* LISTEN
> tcp 0 0 *:http *:* LISTEN
> tcp 0 0 *:x11 *:* LISTEN
> tcp 0 0 *:ftp *:* LISTEN
> tcp 0 0 *:ssh *:* LISTEN
> tcp 0 0 localhost.localdom:smtp *:* LISTEN
> tcp 0 0 *:https *:* LISTEN
> tcp 0 0 192.168.0.171:ssh 192.168.0.1:3294
> ESTABLISHED
>
> When you look at the output from both, there are entries for port 443 and
> https, both in a Listen state. To the untrained eye of mine, it appears
> that Apache is listening to port 443.
>
> Thanks all for the past and future help!!!!
>
> Scott
>
> -----Original Message-----
> From: Lee Fellows [mailto:lfellows@4lane.com]
> Sent: Wednesday, April 24, 2002 9:32 AM
> To: users@httpd.apache.org
> Subject: RE: FW: Apache 1.3.24 & mod_ssl
>
>
> Scott,
>
> 127.0.0.1 is localhost on any machine running an IP stack. Hence
> your Windows 2000 host is attempting to connect to itself, not the
> Linux box, if you issue an http://127.0.0.1/ or https://127.0.0.1/.
> Try running /sbin/ifconfig -a on your Linux host to see what network
> interfaces are defined. You should see something like eth0 with a
> defined IP address. Try using this one.
>
>
>
> On Tue, 2002-04-23 at 23:07, Scott Seidl wrote:
> > 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
> > ##
> > <IfDefine SSL>
> > Listen 80
> > Listen 443
> > </IfDefine>
> >
> > 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Scott Seidl <ap...@worldnet.att.net>.
Thanks for all the sugestions. I misunderstood exactly how the Windows 2000
Gateway worked. Thanks for clearing it up a bit.
As for the correct IP (found by running /sbin/ifconfig -a as suggested by
Lee) it came up with the 192.168.0.171. Again, using this IP I can reach
the introductory apache page through http but not https.
When I run "netstat -na | grep LIST" as suggested by Jack, I get the
following output:
tcp 0 0 127.0.0.1:32768 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
unix 2 [ ACC ] STREAM LISTENING 1203 /dev/gpmctl
unix 2 [ ACC ] STREAM LISTENING 1381 /tmp/.X11-unix/X0
unix 2 [ ACC ] STREAM LISTENING 1302
/tmp/.font-unix/fs7100
unix 2 [ ACC ] STREAM LISTENING 1280
/var/lib/mysql/mysql.sock
When I run "netstat -a | grep 443" as suggested by Owen, I get no ouput.
When I remove the grep 443, I get the following output:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost.localdo:32768 *:* LISTEN
tcp 0 0 *:32769 *:* LISTEN
tcp 0 0 *:mysql *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:http *:* LISTEN
tcp 0 0 *:x11 *:* LISTEN
tcp 0 0 *:ftp *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 localhost.localdom:smtp *:* LISTEN
tcp 0 0 *:https *:* LISTEN
tcp 0 0 192.168.0.171:ssh 192.168.0.1:3294
ESTABLISHED
When you look at the output from both, there are entries for port 443 and
https, both in a Listen state. To the untrained eye of mine, it appears
that Apache is listening to port 443.
Thanks all for the past and future help!!!!
Scott
-----Original Message-----
From: Lee Fellows [mailto:lfellows@4lane.com]
Sent: Wednesday, April 24, 2002 9:32 AM
To: users@httpd.apache.org
Subject: RE: FW: Apache 1.3.24 & mod_ssl
Scott,
127.0.0.1 is localhost on any machine running an IP stack. Hence
your Windows 2000 host is attempting to connect to itself, not the
Linux box, if you issue an http://127.0.0.1/ or https://127.0.0.1/.
Try running /sbin/ifconfig -a on your Linux host to see what network
interfaces are defined. You should see something like eth0 with a
defined IP address. Try using this one.
On Tue, 2002-04-23 at 23:07, Scott Seidl wrote:
> 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
> ##
> <IfDefine SSL>
> Listen 80
> Listen 443
> </IfDefine>
>
> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Lee Fellows <lf...@4lane.com>.
Scott,
127.0.0.1 is localhost on any machine running an IP stack. Hence
your Windows 2000 host is attempting to connect to itself, not the
Linux box, if you issue an http://127.0.0.1/ or https://127.0.0.1/.
Try running /sbin/ifconfig -a on your Linux host to see what network
interfaces are defined. You should see something like eth0 with a
defined IP address. Try using this one.
On Tue, 2002-04-23 at 23:07, Scott Seidl wrote:
> 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
> ##
> <IfDefine SSL>
> Listen 80
> Listen 443
> </IfDefine>
>
> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: FW: Apache 1.3.24 & mod_ssl
Posted by Owen Boyle <ob...@bourse.ch>.
Scott Seidl wrote:
>
> 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.
This isn't right. 127.0.0.1 on ALL systems (linux or windows) is a
loopback address (localhost). i.e. it is an IP address which allows
processes on the same machine to communicate. It can NEVER be used
across a network.
> 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.
It seems that you are simply not listening to port 443. To check this do
"# netstat -a | grep 443" and look for a process binding to 443.
You are starting apache with SSL, I hope (i.e. apachectl startSSL or
httpd -DSSL or something - you have to pass the environment variable
"SSL" to apache if you use <IfDefine>).
Rgds,
Owen Boyle.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Scott Seidl <ap...@worldnet.att.net>.
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
##
<IfDefine SSL>
Listen 80
Listen 443
</IfDefine>
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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Lee Fellows <lf...@4lane.com>.
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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Scott Seidl <ap...@worldnet.att.net>.
I used the url of https://isaartrailriders.dyndns.org which I have as a
domain name (along with localhost.localdomain) of the computer, and that
worked fine. I then tried accessing the same url from my windows box and it
did not work, even though I have a dynamic dns entry that keeps the ip to
that address up-to-date. Could there be a conflict since I have both (the
server and dyndns entry as isaartrailriders.dyndns.org)
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...
I don't believe I tried using the ip address of the Linux box, so that is
something I will try.
Please note, 99% of the time, I access my Linux box through SSL, so
everything need to be configured from the command line.
Again, thanks for the help and future help.
Scott
-----Original Message-----
From: Lee Fellows [mailto:lfellows@4lane.com]
Sent: Tuesday, April 23, 2002 7:23 AM
To: users@httpd.apache.org
Subject: RE: FW: Apache 1.3.24 & mod_ssl
When you state you can see the page when accessing it from the box
itself, do you mean by using a url like 'https://localhost/'? If this
works locally, what are you using for a url from the box where it
fails? You can look at the access_log and error_log to see if apache
is recognizing the connection attempt. The error message you report
seems vague, but I may be mistaken. I am wondering if there is a name
resolution problem from the other box. Did you try using the IP
address of the web server from the other box?
On Mon, 2002-04-22 at 22:16, Scott Seidl wrote:
> I did use the apachectl startssl. I have noticed one thing. If I access
> the page directly from the box, https then works. But if I try accessing
it
> from another machine, I get page can not be displayed.
>
> Any additional help is welcome!
>
> Scott
>
> -----Original Message-----
> From: Lee Fellows [mailto:lfellows@4lane.com]
> Sent: Monday, April 22, 2002 8:37 AM
> To: Apache
> Subject: Re: FW: Apache 1.3.24 & mod_ssl
>
>
> How did you start apache? With apachectl startssl or httpd -DSSL or
> something else? By your configuration SSL will only be available if
> the variable SSL has been defined when starting apache. This is usually
> accomplished by using either of the above mentioned methods.
>
>
> On Sun, 2002-04-21 at 13:07, Scott Seidl wrote:
> >
> > > I have just configured Apache 1.3.24 and mod_ssl. I can connect to
the
> > > url thru normal http just fine, but when I try to use https or port
443,
> I
> > > get page cannot be displayed. I double check the httpd.conf file to
> > > ensure that it was listening to port 80 and 443 under the <IfDefine
SSL>
> > > tag (see segment below).
> > >
> > > Is there anything else that I should check to find out why I can't
reach
> > > the site with https?
> > >
> > > #
> > > # 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
> > > ##
> > > <IfDefine SSL>
> > > Listen 80
> > > Listen 443
> > > </IfDefine>
> > >
> > > Thanks
> > > Scott
> > >
> > > -----------------------------------------------------------
> > > Scott Seidl
> > > Secretary of the Isaar Trail Riders Snowmobile Club
> > > Seymour, Wisconsin
> > > ------------------------------------------------------------
> > > Email: secretary@isaartrailriders.com
> > > Web Address: www.isaartrailriders.com
> > >
> > >
> > ----
> >
>
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
Project.
> > See <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Lee Fellows <lf...@4lane.com>.
When you state you can see the page when accessing it from the box
itself, do you mean by using a url like 'https://localhost/'? If this
works locally, what are you using for a url from the box where it
fails? You can look at the access_log and error_log to see if apache
is recognizing the connection attempt. The error message you report
seems vague, but I may be mistaken. I am wondering if there is a name
resolution problem from the other box. Did you try using the IP
address of the web server from the other box?
On Mon, 2002-04-22 at 22:16, Scott Seidl wrote:
> I did use the apachectl startssl. I have noticed one thing. If I access
> the page directly from the box, https then works. But if I try accessing it
> from another machine, I get page can not be displayed.
>
> Any additional help is welcome!
>
> Scott
>
> -----Original Message-----
> From: Lee Fellows [mailto:lfellows@4lane.com]
> Sent: Monday, April 22, 2002 8:37 AM
> To: Apache
> Subject: Re: FW: Apache 1.3.24 & mod_ssl
>
>
> How did you start apache? With apachectl startssl or httpd -DSSL or
> something else? By your configuration SSL will only be available if
> the variable SSL has been defined when starting apache. This is usually
> accomplished by using either of the above mentioned methods.
>
>
> On Sun, 2002-04-21 at 13:07, Scott Seidl wrote:
> >
> > > I have just configured Apache 1.3.24 and mod_ssl. I can connect to the
> > > url thru normal http just fine, but when I try to use https or port 443,
> I
> > > get page cannot be displayed. I double check the httpd.conf file to
> > > ensure that it was listening to port 80 and 443 under the <IfDefine SSL>
> > > tag (see segment below).
> > >
> > > Is there anything else that I should check to find out why I can't reach
> > > the site with https?
> > >
> > > #
> > > # 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
> > > ##
> > > <IfDefine SSL>
> > > Listen 80
> > > Listen 443
> > > </IfDefine>
> > >
> > > Thanks
> > > Scott
> > >
> > > -----------------------------------------------------------
> > > Scott Seidl
> > > Secretary of the Isaar Trail Riders Snowmobile Club
> > > Seymour, Wisconsin
> > > ------------------------------------------------------------
> > > Email: secretary@isaartrailriders.com
> > > Web Address: www.isaartrailriders.com
> > >
> > >
> > ----
> >
>
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server Project.
> > See <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
RE: FW: Apache 1.3.24 & mod_ssl
Posted by Scott Seidl <ap...@worldnet.att.net>.
I did use the apachectl startssl. I have noticed one thing. If I access
the page directly from the box, https then works. But if I try accessing it
from another machine, I get page can not be displayed.
Any additional help is welcome!
Scott
-----Original Message-----
From: Lee Fellows [mailto:lfellows@4lane.com]
Sent: Monday, April 22, 2002 8:37 AM
To: Apache
Subject: Re: FW: Apache 1.3.24 & mod_ssl
How did you start apache? With apachectl startssl or httpd -DSSL or
something else? By your configuration SSL will only be available if
the variable SSL has been defined when starting apache. This is usually
accomplished by using either of the above mentioned methods.
On Sun, 2002-04-21 at 13:07, Scott Seidl wrote:
>
> > I have just configured Apache 1.3.24 and mod_ssl. I can connect to the
> > url thru normal http just fine, but when I try to use https or port 443,
I
> > get page cannot be displayed. I double check the httpd.conf file to
> > ensure that it was listening to port 80 and 443 under the <IfDefine SSL>
> > tag (see segment below).
> >
> > Is there anything else that I should check to find out why I can't reach
> > the site with https?
> >
> > #
> > # 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
> > ##
> > <IfDefine SSL>
> > Listen 80
> > Listen 443
> > </IfDefine>
> >
> > Thanks
> > Scott
> >
> > -----------------------------------------------------------
> > Scott Seidl
> > Secretary of the Isaar Trail Riders Snowmobile Club
> > Seymour, Wisconsin
> > ------------------------------------------------------------
> > Email: secretary@isaartrailriders.com
> > Web Address: www.isaartrailriders.com
> >
> >
> ----
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: FW: Apache 1.3.24 & mod_ssl
Posted by Lee Fellows <lf...@4lane.com>.
How did you start apache? With apachectl startssl or httpd -DSSL or
something else? By your configuration SSL will only be available if
the variable SSL has been defined when starting apache. This is usually
accomplished by using either of the above mentioned methods.
On Sun, 2002-04-21 at 13:07, Scott Seidl wrote:
>
> > I have just configured Apache 1.3.24 and mod_ssl. I can connect to the
> > url thru normal http just fine, but when I try to use https or port 443, I
> > get page cannot be displayed. I double check the httpd.conf file to
> > ensure that it was listening to port 80 and 443 under the <IfDefine SSL>
> > tag (see segment below).
> >
> > Is there anything else that I should check to find out why I can't reach
> > the site with https?
> >
> > #
> > # 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
> > ##
> > <IfDefine SSL>
> > Listen 80
> > Listen 443
> > </IfDefine>
> >
> > Thanks
> > Scott
> >
> > -----------------------------------------------------------
> > Scott Seidl
> > Secretary of the Isaar Trail Riders Snowmobile Club
> > Seymour, Wisconsin
> > ------------------------------------------------------------
> > Email: secretary@isaartrailriders.com
> > Web Address: www.isaartrailriders.com
> >
> >
> ----
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> 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 <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org