tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: Serve same content to multiple URL's
Date Thu, 04 Apr 2013 21:17:47 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Chris,

On 4/4/13 4:21 PM, Chris Arnold wrote:
> On Apr 4, 2013, at 2:38 PM, "Christopher Schultz"
> <chris@christopherschultz.net> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> Chris,
>> 
>> On 4/4/13 12:28 PM, Chris Arnold wrote:
>>> 
>>> I have tried to add a second worker (worker2) in
>>> workers.properties and added a virtualhost like: Here is the
>>> configured virtualhost for domain2: 2nd virtualhost: JkMount
>>> /share|/* worker2 RedirectMatch ^/$
>>> http://share.domain2.com/share/
>> 
>> If you want the content to be identical, why do you need a second
>> worker?
> 
> I didn't think I needed a second worker but because the working
> config only worked for http://share.domain1.com and nothing else, I
> wanted to verify it should work or I needed another worker and you
> verified I do not need another worker and in fact, the existing
> config for http://share.domain1.com should work for
> http://share.domain2.com

You definitely don't need a second worker.

>> Why do you need a second VirtualHost, even?
> 
> Apache has to answer for that request (http://share.domain2.com)
> and pass it to tomcat

Sure, but you don't care what the target of the request is: everything
goes to the same backend, right?

>>> When i type http://share.domain2.com i arrive at 1 of our
>>> websites but not the tomcat content. When i type 
>>> http://share.domain2.com/share i get a 404 error. Do i need to 
>>> define another worker to accomplish this or should the defined 
>>> worker work for any domain given there is a virtualhost
>>> defined?
>> 
>> Workers don't care about VirtualHosts: the client's request
>> headers will be sent to Tomcat and another round of virtual host
>> resolution will occur over there. Having separate workers does
>> not help anything.
>> 
>> I'm not sure why you are getting 404s: any idea if it's a
>> response coming from httpd or Tomcat?
> 
> No error logs in apache or tomcat which is weird?

Well, httpd should have something in its access log. Does Tomcat have
anything in its access log? If not, then httpd is returning the 404
and you don't have your mod_jk configuration correct. Can you post
more of your httpd.conf? Where do you have JkWorkersFile configured?

>> If you browse to http://share.domain2.com/ are you properly
>> redirected (as I would expect given the above configuration) to
>> http://share.domain2.com/share ?
> 
> It doesn't appear so as a apache site answers the request.

Apache httpd should be answering the request and responding with a
redirect. Does the redirect happen (check your URL bar, or use a
protocol sniffer like HttpFox, etc. through your web browser).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJRXe37AAoJEBzwKT+lPKRYGfIP/iHb43djVfRdbAXDJSdbw598
L7DAZJrPkP6ttM0LLMjH9Iej7s1VMnY/3hVg5Yj/s1yh6kBi/vGt/BQubd5OcpxG
ah7XBGEy+fcV2pYvY6aE4cNj7zVUaabCUuR+dzdCeBB3b36PafPLnDyUxfBNzrK8
n3HqzfG4LrBiufmTZjTeIolD6V13ktt6aX7NJIC7exreATPQQPAJ4ztvdxbC1eRP
jrgEcG4Wh4gWsvW6jSiiRTeVLOg2DrWKTQ76/BD0DBxIYXPHMMR8JjTxMKEBAv5X
Om4LjWrbXPRpCBG1IsdPJaK8Xx+gWycvvzT5RGuFYwRsyeQe6LFhdip0k+T9TGvL
VxFE/N/aywY8r1a+Eg86SjRJnVPkVCrkyR33VtiXa76FMILq90BMqHHpK+i9aAx+
3pplfQYfmCGlGoJYg1Sjap8oPknz2Duundjj2+EAe1oE3ELL53XSbcRJYMgk6Ywq
phXYjIkLlKkl1h1uqDABxpirTBe2DEUS9FgPl8Mp7J3ASrKdDuIlxgmd9TDBqq7W
qMOUYseqHcbUIy+3NwE+8vF2u91/LJUMqHA/8P2iuvnJJyXVyptwKaas8G7Vbl50
vcCVJTeGJgn4h98Wqjm9CFW7dYKIwhJOhkyvzTUfSXWC3t3wukvA+/5k1Jx9oBPD
HOSzSP1UI9ugHxdeRUbN
=+DPt
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message