[Gllug] Problem with Apache & Virtual Hosting

[Jake Jellinek]

Hi,

Are you defining your VirtualHosts by IP address or by name? If you are 
defining by name, then you are reliant on a good/fast DNS lookup every time 
you reload.

See: http://httpd.apache.org/docs/dns-caveats.html

Of course if you're using some versions of mod_frontpage, you'll find that 
MS mistakenly wants you to define your vhosts incorrectly by name, so 
you'll have a little problem, but don't make me go there.

Oh, and get some more memory!

Cheers,

Jake.




--On 15 October 2001 17:00 +0100
--Rowan Puttergill apparently said about the subject "RE: [Gllug] Problem 
with Apache & Virtual Hosting":

> The machine seems to be pretty stable... although fairly low-spec Pentium
> 350 with 64MB RAM.
> Not using any mod-rewrites... so I'm stumped there.
> Definitely not a browser issue... tested with telnet to port 80
> Not using a proxy...
> I'm guessing that it may have something to do with child processes spawned
> by apache or something
> but not sure. Thanks for the help though...
> Ciao
> Rowan
>
> -----Original Message-----
> From: gllug-admin at linux.co.uk [mailto:gllug-admin at linux.co.uk]On Behalf
> Of Alex Hudson
> Sent: 15 October 2001 16:47
> To: gllug at linux.co.uk
> Subject: Re: [Gllug] Problem with Apache & Virtual Hosting
>
>
> On Monday 15 October 2001 16:24, you wrote:
>> When I start Apache, my virtual hosting seems to work fine
>> for a couple of hours or so... then it starts wierding out by either
>> dropping the virtual hosting directives entirely, or by associating the
>> wrong paths with the virtual host in question. A simple restart of Apache
>> usually resolves it, but I have to restart Apache at least once a day.
>
> Apache shouldn't be doing this (and, I would bet, isn't). Is the machine
> it runs on generally stable? This could be a sign of RAM slowly going.
>
> Also, are you using any kung-fu mod_rewrite rules, or something like that?
> The fact that something which did work then breaks means that the
> configuration is changing somehow - I don't think that's an Apache thing.
>
> I would also check that Apache is actually serving the right stuff by
> using telnet to port 80 - it could be your browser (or, more likely,
> proxy, if you have one) that could be dropping the Host: info.
>
> Cheers,
> 			Alex.
>
> --
> Gllug mailing list  -  Gllug at linux.co.uk
> http://list.ftech.net/mailman/listinfo/gllug
>
>
> --
> Gllug mailing list  -  Gllug at linux.co.uk
> http://list.ftech.net/mailman/listinfo/gllug
>



-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug