First thing I would do is drop the wildcard from ServerAlias. There's a very good chance that's an Apache thing...that doesn't necessarily mean that Tomcat accepts it.
Right. Is there any way of figuring out whether Tomcat accepts it? Either
way, it seemed to respond equally to requests that were called through the
alias and through the servername
Not that I know of, short of checking the source or asking on tomcat-dev.
Since your Tomcat instance serves all the requests correctly, the culprit
is Apache not passing the correct host header to Tomcat (or rather, the
host header that Tomcat needs to see). This may or may not be a mod_jk
issue, too.
First thing I did was to have a chat with the Apache folks, and they recommended I had a chat with the mod_jk2 crew as they could not find any problems.
Is there any way I can monitor what headers are sent to mod_jk2 and what headers are sent from mod_jk2?
Not that I know of...the "debug" level for JK logging doesn't list the host headers, as far as I know. I guess you could always tweak the JK/JK2 source to do so, and compile your own version...shouldn't be too difficult. The other thing would be to check Tomcat's logs when requests come in...Tomcat should log 404s, etc. just as Apache does, along with the request URI.
Someone else may have better suggestions. I don't use JK2, but AFAIK name- based virtual hosting works...I know it works with JK.
John
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
