Under both Solaris 2.4 and Linux (tried 2.0.12, 2.0.13, 2.0.14 and now on
2.0.17) Apache 1.1.1, when configured with several virtual hosts (IP based)
it seems to fail to associate the incoming connection with the right config
data sometimes. It reports the objects missing and logs in the wrong file
(I have each virtual host going to its own log file) so it looks a lot like
the destination IP address and/or the port number is being picked up wrong.
In the Solaris case, I have the main server address and 4 additional addresses
each listening on ports 80 and 280. The additional addresses are all setup
to redirect to another server elsewhere (specific subdirectories for each).
The main server works OK on port 80 and not at all on port 280. But the
redirected ones work fine on both 80 and 280. I juggled the configuration
for a test and made different host/port combinations do different things
and it's always port 280 on the main IP address not recognized.
In the Linux case, I have the main server using ports 80, 280, and 1080,
as well as 2 additional hosts only doing port 80. This one is more weird
because sometimes port 80 on the main address works and sometimes not.
The other addresses work.
Mail me if you want to see the config file(s). I have everything put in
a single httpd.conf file instead of three files, for easier managing. I
hope that isn't the cause of the problem.
Phil Howard KA9WGN +---------------------------------------------+
Unix/Internet/System Admin | When freedom is outlawed.... |
CLR/Fast-Tax | ....only outlaws will be free! |