Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Fri, 1 Nov 2013 13:16:20 -0400 (EDT)
From: Chris Arnold <carnold@electrichendrix.com>
To: Tomcat Users List <users@tomcat.apache.org>
Message-ID: <1831730835.84840.1383326180741.JavaMail.root@electrichendrix.com>
In-Reply-To: <52738468.60404@internetallee.de>
References: <1943512527.18194.1379102725857.JavaMail.root@electrichendrix.com>
 <5267E74D.5030008@christopherschultz.net>
 <1392742335.150776.1382544360130.JavaMail.root@electrichendrix.com>
 <52680E93.4060800@christopherschultz.net>
 <1840147813.78648.1383243416757.JavaMail.root@electrichendrix.com>
 <C2DA492BBE9AD2489583E1F6C10E92E507BA4463FD@USEXCMS1.dunnhumby.co.uk>
 <774947895.78871.1383247854986.JavaMail.root@electrichendrix.com>
 <52738468.60404@internetallee.de>
Subject: Re: Multi-URL Access 1 Webapp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: Multi-URL Access 1 Webapp
Thread-Index: q50S4G1GYR5sF172jiQW0S5eac0LDg==

Am 31.10.2013 20:30, schrieb Chris Arnold:
>> mod_rewrite is what's adding the extra /share/
>> RewriteRule ^/(.*) https://192.168.123.3:8443/share/$1 [P]
>> should be something like either:
>> RewriteRule ^/(.*) https://192.168.123.3:8443/$1 [P]
> This takes me to the tomcat home page, /
If you want to be redirected to /share when the user typed /, you could 
add a rewrite rule like
RewriteRule ^/$ /share [R,L]
This will match only on "/".
>
>> or:
>> RewriteRule ^/share/(.*) https://192.168.123.3:8443/share/$1 [P]
> This one gives me a 403 access denied

Here is a response from the apache list:
<snip>
what is happening is when you go to https://share.example.com, Tomcat tries to redirect you to /xxx/xxx/
If you go directly to https://share.example.com/2ndpage/ then you get the login form, but none of the resources (images, css) that should go along with it.
(I do not know why proxy is not working directly to the root, it would probably be a lot of trouble to investigate.)

In general, that is the point of ProxyPassReverse: to catch this type of response and rewrite it. We did not look at that much, but it could potentially solve the problem.
I suspect it would need to be something like (one or both, depending on exactly what is happening)
ProxyPassReverse / https://192.168.123.3:8443/xxx/
ProxyPassReverse / https://share.example.com/xxx/

Another option is to look for a setting in Tomcat that would remove /xxx. I don't know anything about alfresco, so I am not sure where to start with that.

A third option might be to use mod_jk instead of Proxy, but I don't know exactly how to do that either.
</snip>

So i was not able to get any of those to work. So i moved to the third option, mod_jk. It is loaded. I make the changes in my vhost:
        #This rewrites https://share.anydomain.tld to our share server
	RewriteEngine On
	RewriteCond %{HTTP_HOST} ^share\.
	RewriteCond %{HTTPS} on
	RewriteRule ^/(.*) ajp://192.168.123.3:8443/share/$1 [P]

This gives internal server error 500 when going to https://share.example.com. Here are the apache logs:

Fri Nov 01 12:49:32 2013] [notice] Apache/2.2.12 (Linux/SUSE) mod_ssl/2.2.12 OpenSSL/0.9.8j-fips mod_jk/1.2.26 PHP/5.2.14 with Suhosin-Patch mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations
[Fri Nov 01 12:49:41 2013] [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:49:41 2013] [warn] proxy: No protocol handler was valid for the URL /error/HTTP_INTERNAL_SERVER_ERROR.html.var. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:50:07 2013] [warn] proxy: No protocol handler was valid for the URL /share/page/. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:50:07 2013] [warn] proxy: No protocol handler was valid for the URL /error/HTTP_INTERNAL_SERVER_ERROR.html.var. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:50:07 2013] [warn] proxy: No protocol handler was valid for the URL /favicon.ico. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:50:07 2013] [warn] proxy: No protocol handler was valid for the URL /error/HTTP_INTERNAL_SERVER_ERROR.html.var. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:50:07 2013] [warn] proxy: No protocol handler was valid for the URL /favicon.ico. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
[Fri Nov 01 12:50:07 2013] [warn] proxy: No protocol handler was valid for the URL /error/HTTP_INTERNAL_SERVER_ERROR.html.var. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule

How can i get users to type in http://share.example.com and this land on https://share.example.com/xxx/xxx?

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