IIRC, there is no requirement. But from a mapping point of view, the
name used should match what the browser is sending in the "Host:" field.
Tomcat (iirc) doens't do any lookups based on the name field for Host so
from that point of view - life in DNS is OK.
But to access the tomcat server - the user needs to type some address
(name/ip) into the browser.
Where I am going with this is the chance of odd side effect. Let's say
we choose "default" as the host name. So for some reason (where I can't
think of a use case) - the admin then types in http://default/ to their
browser. Their browser does the DNS lookup and goes to whatever DNS
says. Which is probably not the tomcat instance.
So long story short ... my worry is a stretch, bordering fantasy-land.
(which is why i am -0 but swayable) But in apache, there used to be
warnings in various configs about using host names in various places
instead of IP addresses due to relying on DNS.
-Tim
On 7/15/2010 11:11 AM, Mark Thomas wrote:
On 15/07/2010 15:16, Tim Funk wrote:
-0
Since the host name should be a valid dns name(ok it doesn't need to be
a valid dns name if <Alias> is used), choosing a default which doesn't
have a valid dns name may cause woes.
If it does need to be a valid dns name then localhost absolutely makes
sense. Where is that requirement coming from? I can think of anywhere
off the top of my head.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
