Thanks Patrick... then as suspected, I must have a misconfiguration: <Host name="mydomain.com" debug="0" appBase="webapps/mdom" unpackWARs="true" autoDeploy="true">
<Context path="" docBase="" debug="0" reloadable="true" crossContext="true"> <Alias>www.mydomain.com</Alias> ... Now the index.jsp in mydomain.com (forwards to a servlet) works ok, but when I try www.mydomain.com, I get a 404 requested resource (/index.jsp) is not available. Any suggestions why this is occurring are much appreciated, /j-p. On Mon, 24 Nov 2003, Patrick Willart wrote: > Hi JP, > > You don't need to do that. The Alias directive is able to do this. > > <Alias>111.111.111.111</Alias> > <Alias>mydomain.com</Alias> > <Alias>www.mydomain.com</Alias> > > > In order that a virtual host respond correctly to urls: > > http://mydomain.com > > http://www.mydomain.com > > I've had to add two host entries in server.xml (one for mydomain.com, the > other for www.mydomain.com). > > I thought it would have been enough to add the alias directive for the > www.mydomain.com in the mydomain.com host, thereby avoiding duplication > within server.xml? > > Are there problems with the alias directive - or am I misinterpreting it's > function? Is it just that my configuration is probably bad? > > Versions: Tomcat 4.1.24 standalone on redhat 9 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]