Then my conclusion was premature. I stand corrected!
Tim
On 1/20/2012 5:50 PM, Christopher Schultz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim,
On 1/20/12 11:30 AM, Tim De Pauw wrote:
Not sure; a quick test seemed to suggest this, but I may have been
doing something wrong. If I have two hosts X and Y that resolve to
the same IP, can I still use AJP to forward requests to the
respective Tomcat host?
Absolutely. AJP forwards everything from the web server to Tomcat.
Tomcat can determine which virtual host should service the request
just like the web server can.
Regardless, I came across an old discussion [1], which suggests
implementing a servlet filter to check the authenticated user
against an ACL, and throwing a 403 if necessary. I hacked a filter
together, placed the class file under
/webapps/manager/WEB-INF/classes, mapped it to /text/* in
/webapps/manager/WEB-INF/web.xml, and I was good to go!
That will definitely work.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8Zm3AACgkQ9CaO5/Lv0PDwsACfaY5OJYMt5jPms9Y3vxB3YcYe
sNsAni3yxlXvaSwkZYBJ0THRN0DubbKU
=E9d/
-----END PGP SIGNATURE-----
--
Tim De Pauw <tim.dep...@hogent.be>
Vakgroep Informatica
Geassocieerde faculteit Toegepaste Ingenieurswetenschappen
Hogeschool Gent
http://tiwi.be/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org