> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Tuesday, March 15, 2011 3:02 AM
> To: Tomcat Users List
> Subject: Re: Typical setting for
>
> On 15/03/2011 06:06, Jason Pringle wrote:
> > Clearly what is there is correct, since it
On 15/03/2011 15:01, Christopher Schultz wrote:
> For instance, I guess the hostnames are stored in a Map keyed on
> lowercase hostname, and each request does a lookup in that Map to
> determine the host that will handle the request. If the result is null,
> you choose the defaulHost.
Nope. It isn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 3/15/2011 6:02 AM, Mark Thomas wrote:
> On 15/03/2011 06:06, Jason Pringle wrote:
>> Clearly what is there is correct, since it takes some extra effort to embed
>> a Host header into the HTTP request if you don't have a DNS entry (messing
>
On 15/03/2011 06:06, Jason Pringle wrote:
> Clearly what is there is correct, since it takes some extra effort to embed a
> Host header into the HTTP request if you don't have a DNS entry (messing with
> /etc/hosts would be one way). But that last bit of info for how Tomcat
> actually makes use
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Friday, March 11, 2011 10:14 AM
> To: Tomcat Users List
> Subject: Re: Typical setting for
>
> You can call it DefaultHost if you like. The only requirement is that
> the defaultHost specified in the Engine must
On 11/03/2011 18:07, Jason Pringle wrote:
> What are the advantages or requirements (if any) for using a value other than
> localhost, if not using virtual hosts? And if I read the docs correctly, any
> value used must be either a valid IP or resolvable via DNS?
You can call it DefaultHost if y
> From: Jason Pringle [mailto:jason.prin...@amdocs.com]
> Subject: Typical setting for
> What are the advantages or requirements (if any) for using a
> value other than localhost, if not using virtual hosts?
None whatsoever. The character string "localhost" here has n
Tomcat 7.0.6 (soon to upgrade to 7.0.latest)
Fedora 11
JDK 1.6.0_23
We are not using virtual hosts for our tomcat instances, but in some cases run
more than one instance on a machine (listening on different ports). We follow
the typical pattern of a single CATALINA_HOME with distinct CATALINA