That was a serious response I need to investigate before
commenting in detail.
Especially the last paragraph on proxy.
I get that but I don't know the syntax.
I just noticed another pattern from Apache.
blue.ddns.net and brown.ddns.net are routed to
xxxx.ddns.net
but not routed to www.xxxx.org
When setting up virtual host I was not able
give ServerAlias to xxxxx.ddns.net
Apachectl -S gave an error.
www.xxxx.org obviously has one.
So I think that is something to do with the fact ????.ddns.net are not full and proper domains.
P.s. This is Emma,
That is Emily with a protective Daddy, she is working on a school project
emma davis
emma.davis76@xxxxxxx
-----Original Message-----
From: Sander Smeenk <ssmeenk@xxxxxxxxxxxx.INVALID>
To: users@xxxxxxxxxxxxxxxx
Sent: Fri, 7 May 2021 7:02
Subject: Re: apache routing issue
Quoting emma davis (emma.davis76@xxxxxxx.INVALID):
> It is a domain name identification issue by Apache.
> May be it a known issue.
Apache has the concent of a 'default' virtual host. Any request to a
domain not explicitly confiugred for that ip/port combo will be handled
by the defaul virtual host.
See the output of 'apachectl -S'.
If all your vhosts have <VirtualHost *:80>, the first one Apache 'reads'
when parsing the configuration file(s) will be the default for all IPs
on port 80.
This will be why your 'blue' and 'brown' domains show the content of
another site. They are not configured, but some other site on that
ip/port combo was and is considered the 'default' virtual host.
> When it really should be returning a 404 because I haven't set up or
> enabled the blue or brown sites as virtual hosts.
No. It will not return 404.
So you can configure a "no site configured" default virtual host, and
have unconfigured domains land there. And even force it to return a 404.
But Apache, by default, will not do that.
> Conclusion:
> This means I can only host my four websites on one machine.
> If I want the sites to be served from machine B I suspect I will have to
> remove all sites from machine because machine A is taking priority.
If you are behind consumer internet, and you have your router forward
TCP/80 to a certain IP-address, you are limited to that host
(ip-address) handling all HTTP requests. You can however set up a proxy
that deals with routing traffic for certain sites to certain other
ip-addresses in yournetwork. But i think it would be wise to first get a
grip on Apache's essentials before delving in this material.
> emma davis
p.s. do i recall you sending a 'threat' about your daddy being a
barrister who will sue us because some e-mail thread went offline?
-Sndr.
--
| So this magician is walking down the street and turns into a grocery store..
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
