tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier (tomcat)>
Subject Re: Apache mod_jk connector question about alias
Date Thu, 20 Oct 2016 10:19:57 GMT
On 20.10.2016 01:58, Christopher Schultz wrote:
> Hash: SHA256
> Marc,
> On 10/18/16 7:59 PM, Marc Chamberlin wrote:
>> On 10/17/2016 10:36 AM, Rainer Jung wrote:
>>> Alias maps URIs to local file system directories. JkMount maps
>>> URIs to remote back end requests.
>>> You can not change JkMount forwarding using Alias (except that if
>>> you have a comflict between Alias and JkMount only one of them
>>> wins).
>>> As far as I understand you are not really trying to map requests
>>> to the local web server file system, but instead want to forward
>>> to a Tomcat back end but change the URI path which is used when
>>> accessing Apache to something else being used to acces Tomcat.
>>> E.g. the URI /jsp-examples/something gets used when accessing
>>> Apache and mod_jk should send this request as
>>> /examples/jsp/something to the Tomcat back end.
>>> If you really need to change URIs, then often mod_proxy is much
>>> easier to set up, because it has specific directives for this
>>> (ProxyPass etc.).
>>> With mod_jk you would first need to use mod_rewrite RewriteRules
>>> to change the URI, and then JkMount to forward them. More details
>>> can be found at
> 0Rewriting
> The rest of this docs page might be useful as well.
>>> Regards,
>>> Rainer
>> Thanks a million Rainer, you got me over that hump! I have it
>> working now but have another question - When the response is
>> generated for a request, that used the alias in the URL, is there a
>> way to keep the client browser from displaying what the alias got
>> mapped to?
>> So for example, if I use the alias in the URL -
>>  that I send to the Apache
>> server, and it in turn forwards that request to Tomcat as
>>, I would prefer that the
>> response, sent back to the user, contains the original, aliased or
>> unaliased, version of the URL that he/she typed, and not just the
>> resolved version. As it stands I am always getting the response URL
>> of displayed in the client
>> browser.
>> What follows is my current version of the config file that I am
>> using for the jsp-examples. Seems to be working mostly OK, so
>> hopefully I am on the right track. FYI - I intend to include these
>> config files in various virtual hosts configurations each of which
>> have their own document root, hence the reason for the Alias
>> commands at the beginning of this config file.
>> Thanks again in advance for any and all offers of help, thoughts,
>> and replies...
> Your best bet is to name the context in Tomcat to be whatever you
> really want the URL path to be. This will remove all kinds of problems
> you are likely to see in the future because of your decision to try to
> rewrite URLs.
> I never understand why people would rather spend a great deal of time
> configuring around the fact that this simple command will get
> everything working without any other issues:
> $ mv webapps/name-you-have webapps/name-you-want
Because once you start playing with Aliases and RewriteRules, you are setting yourself up

for a lot of future additional complications in terms of Redirects, Authentication, etc..
most of which you cannot even imagine right now.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message