Re: ServletContext and Domains

[Spike Washburn]

What I offered was an interpretation of the spec....how your vendor implemented the servlet engine doesn't necessarily follow my statements.  Some engines may or may not have the flexibility to determine that requests that specify different values in the 'host' header are actually bound for the same virtual host, and therefore the same context.  What you appear to be seeing is that the www.domain.com host and the domain.com host are interpreted by the servlet engine as 2 different hosts and therefore the requests goto 2 different contexts.  If the engine interprets target of these requests as 2 different hosts, then this behavior is correct.  If you mean for the requests to be handled by the same context because you see them as the same host, then you need the engine to support mapping multiple 'host' values to the same context.  Contact your vendor for that.   -Spike ---- Spike Washburn Allaire Corp.      -----Original Message----- From: Lance Lavandowska [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 25, 1999 12:14 PM To: [EMAIL PROTECTED] Subject: Re: ServletContext and Domains Well, we've run some tests, and it appears that it *does* matter what the user enters for the host.  Both addresses are hosted by the same IIS server, and I've set multihoming in JRun for each of them (if memory serves, it didn't work otherwise).   Our servlet checks to see if a ServletContext Attribute has been set, and if not it gets the value and sets it in the ServletContext ("are you there? no? okay, here is what you need").  Whenever it sets the Attribute, it also makes a log entry.    By calling the servlet with and without "www" we were able to see that each time it set the Attribute.   We'll look at having our logging mechanism add the request.getServerName() so that we can be certain. Lance Lavandowska Software Engineer http://www.AgDomain.Com