Re: Multi-URL Access 1 Webapp

2013-11-01 Thread Terence M. Bandoian
On 10/31/2013 2:30 PM, Chris Arnold wrote: >> 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, / > >> or:

Re: Multi-URL Access 1 Webapp

2013-11-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 11/1/13, 5:51 PM, Christopher Schultz wrote: > The above is not using mod_jk. If you are using mod_jk, then you > are either using the "JkMount" directive, or the "SetHandler jk" > directive. Anything else is using mod_proxy_(http|ajp).

Re: Multi-URL Access 1 Webapp

2013-11-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 11/1/13, 1:16 PM, Chris Arnold wrote: > 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: Rewri

Re: Multi-URL Access 1 Webapp

2013-11-01 Thread André Warnier
Chris Arnold wrote: Starting over since i can not seem to get this to work with tomcat or apache. So what i have now that IS somewhat working is: #This rewrites https://share.anydomain.tld to our mail server RewriteEngine On RewriteCond %{HTTP_HOST} ^share\. RewriteCond %{HTTPS}

Re: Multi-URL Access 1 Webapp

2013-11-01 Thread Chris Arnold
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

Re: Multi-URL Access 1 Webapp

2013-11-01 Thread Chris Arnold
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 wa

Re: Multi-URL Access 1 Webapp

2013-11-01 Thread Felix Schumacher
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 re

Re: Multi-URL Access 1 Webapp

2013-10-31 Thread 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, / >or: >RewriteRule ^/share/(.*) https://192.168.123.3:844

RE: Multi-URL Access 1 Webapp

2013-10-31 Thread Matt Barry
want to proxy all URL's to Tomcat, or just the /share ones.. Matt From: Chris Arnold [carn...@electrichendrix.com] Sent: Thursday, October 31, 2013 2:16 PM To: Tomcat Users List Subject: Re: Multi-URL Access 1 Webapp Starting over since i can not s

Re: Multi-URL Access 1 Webapp

2013-10-31 Thread Chris Arnold
Starting over since i can not seem to get this to work with tomcat or apache. So what i have now that IS somewhat working is: #This rewrites https://share.anydomain.tld to our mail server RewriteEngine On RewriteCond %{HTTP_HOST} ^share\. RewriteCond %{HTTPS} on RewriteRule ^/

Re: Multi-URL Access 1 Webapp

2013-10-23 Thread Chris Arnold
If you are sure that httpd Virtual Hosting is working properly (e.g.you can request the proper, say, index.html given a sub-domain), then getting Tomcat to work should not be terribly hard. Can you confirm that VH is working in httpd? Yes, VH's are working fine. We have a number of proxypass/re

Re: Multi-URL Access 1 Webapp

2013-10-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 10/23/13 12:06 PM, Chris Arnold wrote: >> Chris, > >> mod_proxy_ajp and mod_jk are roughly equivalent though with >> wildly differing configuration syntax. Also, mod_jk has quite a >> few additional options that have made it always the ri

Re: Multi-URL Access 1 Webapp

2013-10-23 Thread Chris Arnold
>Chris, >mod_proxy_ajp and mod_jk are roughly equivalent though with wildly >differing configuration syntax. Also, mod_jk has quite a few >additional options that have made it always the right choice for me. >Using mod_rewrite seems completely unnecessary. >Something that you are doing that comp

Re: Multi-URL Access 1 Webapp

2013-10-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 10/23/13 9:07 AM, Chris Arnold wrote: > Hi Matt, > Hi Chris, > You probably want to be using ServerAlias here, iirc.. > > Changed back to ServerAlias > >> #This rewrites https://share.anydomain.tld to our alfresco >> server R

Re: Multi-URL Access 1 Webapp

2013-10-23 Thread Chris Arnold
Hi Matt, >>>Hi Chris, >>>You probably want to be using ServerAlias here, iirc.. Changed back to ServerAlias >#This rewrites https://share.anydomain.tld to our alfresco server >RewriteCond %{HTTP_HOST} ^share\. >RewriteCond %{HTTPS} on >>>Okay, I'll take a bite at the ob

RE: Multi-URL Access 1 Webapp

2013-10-22 Thread Matt Barry
Hi Chris, >>I didn't know you were running a 3rd-party application. Do you need >>the application to behave differently given a particular client? If >>not, there's nothing to do. If so, you probably need to ask the >>Alfresco folks how to do that. I personally know nothing about >>Alfresco, thoug

Re: Multi-URL Access 1 Webapp

2013-10-22 Thread Chris Arnold
>I didn't know you were running a 3rd-party application. Do you need >the application to behave differently given a particular client? If >not, there's nothing to do. If so, you probably need to ask the >Alfresco folks how to do that. I personally know nothing about >Alfresco, though there may be s

Re: Multi-URL Access 1 Webapp

2013-09-17 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 9/16/13 3:42 PM, Chris Arnold wrote: > Chris, > > >>> If you just need 1 deployed webapp, then simply change your >>> webapp to sniff the client's name from the URL. You don't need >>> to change anything: you still only need one (default

Re: Multi-URL Access 1 Webapp

2013-09-16 Thread Chris Arnold
Chris, >>If you just need 1 deployed webapp, then simply change your webapp to >>sniff the client's name from the URL. You don't need to change >>anything: you still only need one (default) virtual host in Tomcat, >>and you can do whatever you want (e.g. single virtual host) in httpd. Maybe i ne

Re: Multi-URL Access 1 Webapp

2013-09-16 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 9/14/13 7:27 PM, Chris Arnold wrote: > Chuck, > > On 9/13/13 4:38 PM, Caldarale, Charles R wrote: >>> From: Chris Arnold [mailto:carn...@electrichendrix.com] >>> Subject: Multi-URL Access 1 Webapp >

Re: Multi-URL Access 1 Webapp

2013-09-14 Thread Chris Arnold
Chuck, On 9/13/13 4:38 PM, Caldarale, Charles R wrote: >> From: Chris Arnold [mailto:carn...@electrichendrix.com] Subject: >> Multi-URL Access 1 Webapp > >> Tomcat 7.0.3 i believe > > Not bloody likely - 7.0.3 was never released. If you really are > running on 7

Re: Multi-URL Access 1 Webapp

2013-09-13 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chuck, On 9/13/13 4:38 PM, Caldarale, Charles R wrote: >> From: Chris Arnold [mailto:carn...@electrichendrix.com] Subject: >> Multi-URL Access 1 Webapp > >> Tomcat 7.0.3 i believe > > Not bloody likely - 7.0.3 was nev

RE: Multi-URL Access 1 Webapp

2013-09-13 Thread Caldarale, Charles R
> From: Chris Arnold [mailto:carn...@electrichendrix.com] > Subject: Multi-URL Access 1 Webapp > Tomcat 7.0.3 i believe Not bloody likely - 7.0.3 was never released. If you really are running on 7.0.3, you need to upgrade ASAP. > We have a web app that you access from http://doma

Multi-URL Access 1 Webapp

2013-09-13 Thread Chris Arnold
Tomcat 7.0.3 i believe on SLES11 SP2. We have a web app that you access from http://domain.tld/share. What we want to do is have clients access the same web app only from http://share.domain.tld. The domain part of that URL will change per client. So, some will get to it like http://share.domain