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
-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
> resp
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?
Regardless, I came across an old discussion [1], which suggests
implementing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim,
On 1/20/12 10:35 AM, Tim De Pauw wrote:
> Multiple hosts probably won't solve this problem either. I'm using
> AJP, which doesn't seem to play well with vhosts.
Wait, what?
In what way does AJP not play well with vhosts?
- -chris
-BEGIN PG
Thanks for your reply.
I don't suppose there's an alternative to the Manager app floating
around that would allow this? I came across a commercial solution at
some point (which I forgot to bookmark, apparently), but that's not
really an option.
Multiple hosts probably won't solve this proble
On 20/01/2012 15:19, Tim De Pauw wrote:
> I assume I'm doing something fundamentally wrong here, but the docs
> don't seem to cover this sort of thing explicitly. I guess I could
> create separate hosts for each app and user, but that seems tedious and
> unnecessary.
>
> Any pointers? Thanks.
You
Hi all,
I'm trying to configure Tomcat so that a separate login is required to
deploy certain apps. Let's say I have a '/someapp' context, which I
would like 'someuser' to deploy remotely. However, 'someuser' cannot
deploy apps to '/someotherapp', and conversely, 'someotheruser' cannot
touch
