> Remy Maucherat wrote:
> >
> > > If you configure both an https(SSL) Host and an http Host which have
> > > the same domain name they end up having the same workDir.
> > >
> > > Using the Host name to create the default workDir does not guarantee
> > > it is unique since their can be both an http host and an https host
> > > with the same domain name.
> > >
> > > There is no easy workaround for this in the current tomcat
configuration
> > > since the workDir can only be configured in the Context scope.
> > >
> > > This case can arise when you use two Engine configurations, one for
> > > http hosts and one for https hosts, each Engine with a separte Ajp
> > > connector to Apache.
> > >
> > > Perhaps the work dir directory path should have an additional
directory
> > > in its path for the Engine name.
> > >
> > > $CATALINA_HOME/work/{engine}/{host}/{webapp}
> >
> > Yes, I know about that issue. I've been saying that the host name should
be
> > unique across all services, which seems reasonable to me.
> > In your example, I think there should be 2 connectors attached to the
same
> > host.
> >
>
> I am not sure how the above would fix the problem I see.
>
> Attaching two connectors to the same host would not fix the problem I
have.
> Because each host (http and https with the same domain name) are a
different
> web site with different content and web applications.

Ok, your use case looks legitimate :-(

I'm -1 for fixing this in 4.0.x (it's just too risky). Fixing it in HEAD is
non trivial (you have to change the work dir, change the JNDI URLs), but
since there are no pending releases, I think it can be done. Using the
engine name or the service name seems reasonable. Which one do you think is
best ? Do you volunteer to do the changes ?

Remy


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to