On Tue, Sep 04, 2001 at 05:07:10PM +0200, Ferenc Engard wrote:
> > Ah, of course. the virtualhost only reacts to request to 192.168.0.1, so
> > the localhost request (to 127.0.0.1) will not be served by that
> > virtualhost entry. Same could be for the external name, if that does not
> > resolv to 192.168.0.1. Make extra virtual host entries for each IP you'd
> > want the host to listen to.
>
> Hmm, another try:
>
> >From a machine on internal network:
>
> http://<my_external_name>/ppteszt2/ ->
>
> 192.168.0.19 - - [04/Sep/2001:17:02:55 +0200] "GET /ppteszt2/ HTTP/1.1"
> 404 296 "-" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
>
> http://linuxserver/ppteszt2/ ->
>
> [...]
> 192.168.0.19 - - [04/Sep/2001:17:03:05 +0200] "GET /ppteszt2/ HTTP/1.1"
> 200 12279 "-" "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)"
> [...]
>
> So, the IP number is the client's IP number, yes?
>
> Anyway, besides this, I think the problem is what you said. Then it is a
> big problem, because my external IP changes, as I use ADSL and dynamic
> DNS.
>
> Hmm, this is the time trying to put more records into 'host' table. :-P
BTW, you could put Midgard's engine On on the default host and manage all
virtual hosts directly from the Midgard database:
<VirtualHost _default_:*>
MidgardEngine On
#other configuration options
</VirtualHost>
Note the absence of ServerName or ServerAlias here.
Then mod_midgard will make decisions for every request but if this server
serves only (or almost all) Midgard sites, that's the easiest
configuration.
--
/ Alexander Bokovoy
$ cat /proc/identity >~/.signature
`Senior software developer and analyst for SaM-Solutions Ltd.`
---
Monday is an awful way to spend one seventh of your life.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
