httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Admin" <>
Subject RE: VitualHost problem finally fixed
Date Wed, 31 Jul 2002 16:48:08 GMT
Zac, I do believe that I'm right about this being a a fix for everyone...
on this specific topic., as i've tried everything...before this.
As has alot of others on this list, with the same problem...and you know
you've seen them yourself. I'm not the only one having this problem.
I've been dealing with a solution to this for quite awhile now.
This fix does work, and should be considered and entered into the apache
Doesn't it ever ocur to you, at all, WHY there is never a answer given, to
this question
and/or problem when others asked for it...and were then told to GO to the
well, it's because they don't know...the answer...
well, NOW they do....thanks to what i found out...

-----Original Message-----
From: Zac Stevens []
Sent: Wednesday, July 31, 2002 2:45 AM
Subject: Re: VitualHost problem finally fixed

On Wed, Jul 31, 2002 at 02:16:53AM -0400, Admin wrote:
> You also must have your BindAddress directive, set as " * "
> and a FQDN  (Fully Qualified Domain Name) set as your "ServerName"
> in the uppermost global config.

As far as I can tell, BindAddress is a wildcard by default.  ie, if you
haven't specifically configured it to something different, httpd will bind
to all addresses on your system.  If this isn't the behaviour you're
seeing, it's a bug with the software - not the documentation.

ServerName needs to be set to a valid FQDN to work properly on the greater
internet (a fact clearly documented in the sample configuration), but this
really only affects the operation of server-generated pages - most notably

> Also no one else has ever mentioned this very important
> fact on this list, at all either. Wonder WHY that is?  eh?
> makes you stop and think, doesn't it? Do these people who claim to
> know this or that, REALLY know what they say, or are they just
> stuck up? selfish people?  You decide....

As noted, while the above may have fixed the problem in your particular
instance, it is by no means general advice which is required for everyone.

Please remember that everyone contributing to this list is a volunteer -
no-one is paid to answer questions here.  Naturally, requests which can be
answered quickly are going to receive better aid than those requiring a lot
of time to look at the configuration and the result you're trying to

Regarding the documentation, if you have suggestions on how it can be
clarified or otherwise improved, the Documentation project would love to
hear them.  You can find details on joining that list here:



To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message