https://issues.apache.org/bugzilla/show_bug.cgi?id=35959
Sven <sven.koeh...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #10 from Sven <sven.koeh...@gmail.com> 2011-10-25 19:03:59 UTC ---
(In reply to comment #9)
> No response in nearly 4 years.
> User didn't provide a concrete use case for the feature.
UseCanonicalName influences things like redirects on the apache side. As far as
I can recall, a redirect will use the canonical name if UseCanonicalName=on.
That behaviour of apache can be totally undesired, since obviously the http
client would be redirected to another domain and therefor cookies will be
invalid
and whatnot.
On the other hand, UseCanonicalName=on was the only way to make sure that a
http-request that matched a certain vhost on the apache site goes to a specific
tomcat vhost. With UseCanonicalName=off you would basically have to adjust the
tomcat config so that resembles the apache config with its servernames and
serveraliases as close as possible. I'm not sure, if the latter is even
possible in any case. The apache configuration language might be more powerful
than the tomcat's.
So with respect to mod_jk, UseCanonicalName=on can be desired while at the
same time UseCanonicalName=off can be desired for redirect on the apache side.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
