Redhat secure server - Aug 1998 - Re: Sharing server/document root?

On Sat, 22 Aug 1998 17:51:08 -0400, Jon Radel wrote:
>At 02:07 AM 8/22/98 -0500, you wrote:
>>On Fri, 21 Aug 1998 23:42:04 -0400 (EDT), Cynthia Dale wrote:
>>
>>>As it says in the manual, section 1.5.3, pages 13 and 14:
>>>"The virtual hosts feature of the Red Hat Secure Web Server
gives you the
>>>flexibility to run different servers for different addresses all on
the
>>>same machine.  Virtual hosts also give you the ability to run both
secure
>>>and non-secure servers on the same machine."
>As I''ve already reported to the "bugs in documentation"
e-mail address, it
>works a lot better if you also have
>
>Listen 80
>Listen 443
>
>in httpd.conf.
Thanks, Jon.  That was the missing ingredient.  Adding those Listens makes
it work fine now.  By the way, I searched the Red Hat bug tracking system
at http://developer.redhat.com/bugs but they don''t have documentation
bugs in their system -- they ought to for something like this.

>While we''re on the topic of things in the manual which
don''t quite work out
>that way in real life, can anyone confirm that mod_perl works for the
>Secure Web Server running under RH Linux 5.1?  I have a fairly vanilla
>Pentium with RH Linux 5.1, with all the appropriate update RPMs applied,
>where mod_perl simply refuses to work.  It''s recognized, when I
have it
>installed mod_perl statements in the Apache configuration files are
>recognized instead of simply resulting in error messages, but any file
>which should be executed is simply served as text/plain of the perl source
>code.  Tech support has yet to answer the simple question of whether it
>works for other people on 5.1.
I can confirm that it fails here under those same conditions with the same
symptoms, regardless of whether it use the ''alias /perl/''
method to make
the directory all perl, or uses the ''files <*.pl>'' to
just make .pl files execute.
Seems like they have a problem or some obscure config trick.


On Sat, 22 Aug 1998 10:49:11 -0400 (EDT), Preston Brown
wrote:
>On Sat, 22 Aug 1998, Jeff Rush wrote:
>
>> Hmmm, I just installed the Secure Server here and uncommented
>> those lines and it doesn''t work.
[snip]
>Simple question, but: Did you restart the server after making changes?
Good question, Preston, but yes, I did.  My fingers have it memorized.
Thanks!

-Jeff Rush

At 08:38 AM 8/24/98 -0500, you wrote:
>Thanks, Jon.  That was the missing ingredient.  Adding those Listens makes
>it work fine now.  By the way, I searched the Red Hat bug tracking system
>at http://developer.redhat.com/bugs but they don''t have
documentation
>bugs in their system -- they ought to for something like this.
E-mail to docs@redhat.com is supposed to serve that purpose.  Just as bugs
in the online errata sheets are supposed to be sent to
faq-maintainer@redhat.com.  I can report that the latter works quite
nicely; a responsive person says, "Ooops, thanks" and before you know
it
the problem is fixed.  The former, I hope goes to some queue for dealing
with later...

I agree that it would be nice to integrate all this with the bug system.

I''ve seen several signs that Red Hat is dealing reasonably well, but
not
perfectly, with their current rate of growth.
>>While we''re on the topic of things in the manual which
don''t quite work out
>>that way in real life, can anyone confirm that mod_perl works for the
>>Secure Web Server running under RH Linux 5.1?  I have a fairly vanilla
>>Pentium with RH Linux 5.1, with all the appropriate update RPMs applied,
>>where mod_perl simply refuses to work.  It''s recognized, when I
have it
>>installed mod_perl statements in the Apache configuration files are
>>recognized instead of simply resulting in error messages, but any file
>>which should be executed is simply served as text/plain of the perl
source
>>code.  Tech support has yet to answer the simple question of whether it
>>works for other people on 5.1.
>
>I can confirm that it fails here under those same conditions with the same
>symptoms, regardless of whether it use the ''alias /perl/''
method to make
>the directory all perl, or uses the ''files <*.pl>''
to just make .pl files
execute.
>Seems like they have a problem or some obscure config trick.
Oh, thank you.  It''s so nice to know that it''s not just
something stupid
that I did.

--Jon Radel
jon@radel.com