Re: Multi-URL Access 1 Webapp
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: >> RewriteRule ^/share/(.*) https://192.168.123.3:8443/share/$1 [P] > This one gives me a 403 access denied > >> ..depending on whether you want to proxy all URL's to Tomcat, or just the >> /share ones.. > Looks like i am back to the apache list > This might help: http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewriterule That's for version 2.4. -Terence Bandoian - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
-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). Apologies, that should have been : " SetHandler jakarta-servlet SetEnv JK_WORKER_NAME my_worker " - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSdCaRAAoJEBzwKT+lPKRYVUcP+QGYk4PoATGximR2Na8jHDc2 +hnPZvwQN582xgzUyfcbWr7W/5VNudhjr2hW/rfdjp/Qq2WcZgImQpKs3AoHBT+C bHj5h9vPEdZnz/96RmZXOi0/apUFT6TorAkhzP/IX5ojtO2h8z74G8Y8/0UqmrT+ AECvkQgTwDN3U3T1vz8g3bboApwlGtjsQ5fkHOTpGkML9q/dePJzVgFJ1JlorrHo AV++TJRTo9knnAXcLXoB4pP3m2cJjN2byyIKL0nQNCB+YgM/cneeGXQeFjsyHJz1 +pJf+Q9ouiVbm/yPxEbYEeaZnYFPXKdZAMtZiFeXMWVxbBMdsPY1nZnqMjXhc9qM 7rW3xxZ9m91p90TP2Y1QLcHvns24qY2D6ZuRnXrRL115yFiFUU8pbtA88NonbOlb A/sXW/XdYGNusVhZqL8MSy44pVgidP4aBMuCnwjIerXbE54WQfFcK9q3aR/nV+RI hj9FDQxzNVkdJD5sd0UNVMcMosCcYfXJQtJ1Ve0R9CkI6y8x34M2wIYaxnkkRE+J dfVhNhIu65KkOxhgE+XloZuN+b5N5RzEUoJ6brNi4ZWmEkMGi078nH5bS+2cOKtD CeJVyC51mIrdD5lOSoMt6ALbK9jZzs4Loq1znStkCnorWVRZ/AjIvSqWtVV7SWqT AshoB/usIBavuSfGtMMm =550X -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
-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: 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: 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.
>
> 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]
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).
> 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
... or not using anything at all. Only mod_proxy_ajp understands
ajp:// URLs.
> How can i get users to type in http://share.example.com and this
> land on https://share.example.com/xxx/xxx?
ServerName share.example.com
RedirectPermanent / https://share.example.com/xxx/xxx?
?
Honestly, I don't know why you don't just use a redirect instead of
trying to modify requests in-flig
Re: Multi-URL Access 1 Webapp
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} on
RewriteRule ^/(.*) https://192.168.123.3:8443/share/$1 [P]
This DOES get me over to the tomcat side but gives a 404. Notice the status
line:
HTTP Status 404 - /share/share/page/
with which *original* request URL ?
Tomcat seems to be adding an extra /share. User need to access the web app with
https://share.anydomain.tld which will land on apache and apache will get it to
tomcat. The web app is accessible from http://ip:8080/share or
https://ip:8443/share. How do i stop tomcat from adding the extra share?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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]
Got it for those of you following or will need this:
#This rewrites https://share.anydomain.tld to our share server
RewriteEngine On
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteCond %{REQUEST_URI} !^/share/
RewriteRule ^/(.*) https://share.example.com:/share/ [P]
JkMount /share/* worker1
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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:
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.
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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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 What happens, if you call the tomcat url directly? Do you get a cookie? If so, which domain is it for? Maybe you have to add another directive to rewrite the cookie domain on the way back through httpd, or alternatively set the right domain in tomcat? For further information you could look at http://tomcat.apache.org/tomcat-7.0-doc/proxy-howto.html. Regards Felix ..depending on whether you want to proxy all URL's to Tomcat, or just the /share ones.. Looks like i am back to the apache list - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
>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:8443/share/$1 [P] This one gives me a 403 access denied >..depending on whether you want to proxy all URL's to Tomcat, or just the >/share ones.. Looks like i am back to the apache list - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multi-URL Access 1 Webapp
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]
or:
RewriteRule ^/share/(.*) https://192.168.123.3:8443/share/$1 [P]
..depending on whether you 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 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 ^/(.*) https://192.168.123.3:8443/share/$1 [P]
This DOES get me over to the tomcat side but gives a 404. Notice the status
line:
HTTP Status 404 - /share/share/page/
Tomcat seems to be adding an extra /share. User need to access the web app with
https://share.anydomain.tld which will land on apache and apache will get it to
tomcat. The web app is accessible from http://ip:8080/share or
https://ip:8443/share. How do i stop tomcat from adding the extra share?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
The contents of this message and any attachments to it are confidential and may
be legally privileged.
If you have received this message in error you should delete it from your
system immediately and advise the sender.
dunnhumby may monitor and record all emails. The views expressed in this email
are those of the sender and not those of dunnhumby.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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 ^/(.*) https://192.168.123.3:8443/share/$1 [P]
This DOES get me over to the tomcat side but gives a 404. Notice the status
line:
HTTP Status 404 - /share/share/page/
Tomcat seems to be adding an extra /share. User need to access the web app with
https://share.anydomain.tld which will land on apache and apache will get it to
tomcat. The web app is accessible from http://ip:8080/share or
https://ip:8443/share. How do i stop tomcat from adding the extra share?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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/reverse, rewrite among other statements in vhost files. These all have worked fine for a number of years.
Re: Multi-URL Access 1 Webapp
-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 right choice >> for me. > >> Using mod_rewrite seems completely unnecessary. > >> Something that you are doing that complicates your configuration >> is trying to map / on httpd to /share on Tomcat. Why not map / to >> / ? All you have to do is re-name your webapp from whatever.war >> to ROOT.war (note capitals are required, even on case-insensitive >> filesystems). > >> With that simplified configuration, you need only do: > >> JkMount /* workerX > >> for mod_jk or > >> ProxyPass / ajp://tomcat-host:tomcat-port/ ProxyReversePass / >> ajp://tomcat-host:tomcat-port/ > >> for mod_proxy_ajp. Or, use mod_proxy_http by using an http:// >> URL instead of ajp://. > > ProxyPass / http://192.168.123.3:8080/ and > http://192.168.123.3:8080/share/ ProxyPassReverse / > http://192.168.123.3:8080/ and http://192.168.123.3:8080/share/ > > do not work. Now i am back to i am not sure if this is a tomcat > problem or an apache problem 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? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIbBAEBCAAGBQJSaA6TAAoJEBzwKT+lPKRYR8kP9j/8Y3NC68M9P/IrGc43800t o//4hL8VO016uRx0VJmmUuqvgJ2dEK9UFnbOAAR2R0Eh1JR4Yucy8CAIzvOx+QiC Y+fnvqHFDzG9Lf4BlX0yv+BS0HYZ4Z0SGogvoMUJ1LE/ItHbXZzofrfSXwdIx8vR i7skbEREu/wufDBzZ8rSys+rOEeqIkG1uHNrU/s30XOaz4pA6SHZ/2bWMlG0xPsC KUAersaMcKGcCLuGeseavWqk9JtkdPy81DY5zbyP+9vZEum2y7O5Zz8Ig3Ixwozu B2WUBj82KDhlIHllpbVeiAeyluN1d5rD8QLZ+GIPiZglnWIVOY8Ciq+YWOva2OZE aRBr8ze8wsrrJGNxRnZu21bWJAXj5G1WPkZmLOxOC8DApPnHuv0peQHUAJpmyeos MjT4ieJuCS+1+mitzcrZyHq4JS9SAZLRBxKq3MV6QVrKMFbbEUJgOvXLkvoarihb 8riyTuhAmhG+OU+zz2SrEnxxXpYMbbyXKK+xv6hsf5tpidBBvVdTR32kXLO0+pH0 ajrxmh40A+3gXxvAljJtF3EdTs8X3HkSPcUNswYYki+tqSar5apfbKI3CH4xgZ88 YIEyP1F0haX3b1c0U8NE0cPXCYUsSAJJa8G7Dng8gIHCyPfTEPnSX8cCcVeVqe/5 Jnd5Nbtr/80QYcKO8AQ= =HJ1W -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
>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 complicates your configuration is >trying to map / on httpd to /share on Tomcat. Why not map / to / ? All >you have to do is re-name your webapp from whatever.war to ROOT.war >(note capitals are required, even on case-insensitive filesystems). >With that simplified configuration, you need only do: > JkMount /* workerX >for mod_jk or > ProxyPass / ajp://tomcat-host:tomcat-port/ > ProxyReversePass / ajp://tomcat-host:tomcat-port/ >for mod_proxy_ajp. Or, use mod_proxy_http by using an http:// URL >instead of ajp://. ProxyPass / http://192.168.123.3:8080/ and http://192.168.123.3:8080/share/ ProxyPassReverse / http://192.168.123.3:8080/ and http://192.168.123.3:8080/share/ do not work. Now i am back to i am not sure if this is a tomcat problem or an apache problem - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
-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 RewriteCond %{HTTP_HOST} ^share\. RewriteCond %{HTTPS} on
>
Okay, I'll take a bite at the obvious. Your vhost is running
on *:80, and your mod_rewrite condition only triggers >>>for
https; is your httpd actually serving https on port 80?
>
> No, that is a copy/paste typo on my part.
>
>> RewriteRule ^/(.*) http://192.168.123.3:8080/share/$1 [P]
>> RedirectMatch ^/$ /share/
>
I sort of doubt that this combination of rewrites and
redirects is going to do what you want. If the RedirectMatch
>>>fires (I'm not positive it would), it would send a 302 to
/share/, which would then get proxied to /share/share/ on
>>>your app server. (This is the type of setup I typically
find mod_proxy much easier to work with vs mod_redirect,
>>>but this is all OT for this list..)
>
> I agree with you on OT. I am trying to determine if this is a
> tomcat issue or an apache issue. A few months back, i asked how to
> go about accomplishing this and i was instructed to config tomcat
> is this manner:
>
> add to httpd.conf = # mod_jk Include
> /opt/alfresco/tomcat/conf/jk.conf
>
> jk.conf =
>
> JkWorkersFile /opt/alfresco/tomcat/workers.properties JkLogFile
> /var/log/alfresco/mod_jk.log JkShmFile /var/log/alfresco/shm
>
> # Log level to be used by mod_jk JkLogLevel error
>
> # The following line prohibits users from directly accessing
> WEB-INF #AllowOverride None deny from
> all
>
>
>
>
> workers.properties = # Define two status worker: # - jk-status for
> read-only use # - jk-manager for read/write use
> worker.list=jk-status worker.jk-status.type=status
> worker.jk-status.read_only=true
>
> worker.list=jk-manager worker.list=worker1
> worker.jk-manager.type=status Plus all the other properties inside
> the file that i wont posted here. Then made an apache vhost file
> like this: ServerAdmin email@address ServerName
> share.server.name
>
> JkMount /share|/* worker1 RedirectMatch ^/$
> http://share.server.name/share/
>
>
>
> This worked for the 1 share.domain.tld so i made other vhosts for
> the other share.domain.tld. The other share.domain.tld's do not
> work using mod_jk. So i am trying to determine if i need to undo
> the mod_jk config and setup straight vhosts. I am using mod_proxy
> with apache
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 complicates your configuration is
trying to map / on httpd to /share on Tomcat. Why not map / to / ? All
you have to do is re-name your webapp from whatever.war to ROOT.war
(note capitals are required, even on case-insensitive filesystems).
With that simplified configuration, you need only do:
JkMount /* workerX
for mod_jk or
ProxyPass / ajp://tomcat-host:tomcat-port/
ProxyReversePass / ajp://tomcat-host:tomcat-port/
for mod_proxy_ajp. Or, use mod_proxy_http by using an http:// URL
instead of ajp://.
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSZ+dNAAoJEBzwKT+lPKRYggsP/jhhKwNcliRX/2IgQHNkizSJ
2j3+se6yb1jOBiIFt82TpTlIN0+JmCqsL5x33aNbxMHr5hVTxWysLjtgrjH0gGI+
GjdpfqbbvwPGdRHkwlLXADeezk9i2uV5xni9zwwFrL0mIfZepo9XPDz4tCS5GMKV
LFNGJlSmGgl8IPZpNpxC+d3q7KLP1iviOhfe8hb1LP2fcEHV3O3ytmpc+1Ul7ASu
lZbKZV+LoW86MIoMT1+615ytFt1wfzgKOZCqEOLLAw84R9Ewa3fLowGfLeODf8WQ
m2OyFZYhgimee1j+/DbSypfICLjaI7gFal+qhNb4hASbyAxJNcUKYR4AzhjOEr1H
rur/hLw5W0ZaUD8GlD5SXtB0I/YpiU45ghLQQjqp4XxPy6dRmGAQ1O0vFWa1t/Ky
5WX8ib0CzU2Kdn86JEx9NPNtAqGlsqpRwXEaDX0Bh92n3e/PTZyC3/qzQQ00QqAB
w4hXtnUlCCMKruKzAdpEsaZiZK5s67oIVXOAWjJcJvFYM3W1hrLfnF7PPUEDQyj4
BfBZTrHFX6XU59A0+poysLq/R/QYqdNWNLkiwW9t6HWE8unPn0kTCtVUGNG3BZRY
Lwd5l2rME1Mm5a3M5atqcUfGx+3+ZQ6tCvaksY7SvKRzy/qFIt4XJjvITuEgcxBg
Of4/be7ir96dYgmiQYn9
=C7/q
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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 obvious. Your vhost is running on *:80, and
>>>your mod_rewrite condition only triggers >>>for https; is your httpd
>>>actually serving https on port 80?
No, that is a copy/paste typo on my part.
>RewriteRule ^/(.*) http://192.168.123.3:8080/share/$1 [P]
>RedirectMatch ^/$ /share/
>>>I sort of doubt that this combination of rewrites and redirects is going to
>>>do what you want. If the RedirectMatch >>>fires (I'm not positive it
>>>would), it would send a 302 to /share/, which would then get proxied to
>>>/share/share/ on >>>your app server. (This is the type of setup I typically
>>>find mod_proxy much easier to work with vs mod_redirect, >>>but this is all
>>>OT for this list..)
I agree with you on OT. I am trying to determine if this is a tomcat issue or
an apache issue. A few months back, i asked how to go about accomplishing this
and i was instructed to config tomcat is this manner:
add to httpd.conf = # mod_jk
Include /opt/alfresco/tomcat/conf/jk.conf
jk.conf =
JkWorkersFile /opt/alfresco/tomcat/workers.properties
JkLogFile /var/log/alfresco/mod_jk.log
JkShmFile /var/log/alfresco/shm
# Log level to be used by mod_jk
JkLogLevel error
# The following line prohibits users from directly accessing WEB-INF
#AllowOverride None
deny from all
workers.properties = # Define two status worker:
# - jk-status for read-only use
# - jk-manager for read/write use
worker.list=jk-status
worker.jk-status.type=status
worker.jk-status.read_only=true
worker.list=jk-manager
worker.list=worker1
worker.jk-manager.type=status
Plus all the other properties inside the file that i wont posted here. Then
made an apache vhost file like this:
ServerAdmin email@address
ServerName share.server.name
JkMount /share|/* worker1
RedirectMatch ^/$ http://share.server.name/share/
This worked for the 1 share.domain.tld so i made other vhosts for the other
share.domain.tld. The other share.domain.tld's do not work using mod_jk. So i
am trying to determine if i need to undo the mod_jk config and setup straight
vhosts. I am using mod_proxy with apache
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multi-URL Access 1 Webapp
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, though there may be some folks on the list who do and might
>>reply here.
>
>I need to revisit this issue. Here is my apache vhost:
>
>ServerName share.*
You probably want to be using ServerAlias here, iirc..
>#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 obvious. Your vhost is running on *:80, and your
mod_rewrite condition only triggers for https; is your httpd actually serving
https on port 80?
>RewriteRule ^/(.*) http://192.168.123.3:8080/share/$1 [P]
>RedirectMatch ^/$ /share/
I sort of doubt that this combination of rewrites and redirects is going to do
what you want. If the RedirectMatch fires (I'm not positive it would), it
would send a 302 to /share/, which would then get proxied to /share/share/ on
your app server. (This is the type of setup I typically find mod_proxy much
easier to work with vs mod_redirect, but this is all OT for this list..)
Cheers,
Matt
The contents of this message and any attachments to it are confidential and may
be legally privileged.
If you have received this message in error you should delete it from your
system immediately and advise the sender.
dunnhumby may monitor and record all emails. The views expressed in this email
are those of the sender and not those of dunnhumby.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
>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 some folks on the list who do and might
>reply here.
I need to revisit this issue. Here is my apache vhost:
ServerName share.*
#This rewrites https://share.anydomain.tld to our alfresco server
RewriteCond %{HTTP_HOST} ^share\.
RewriteCond %{HTTPS} on
RewriteRule ^/(.*) http://192.168.123.3:8080/share/$1 [P]
RedirectMatch ^/$ /share/
This lands on the the apache part not the tomact part (both apache and tomcat
are the same server). We need http://share.*.* to land on the tomcat web app.
Any advise?
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
-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) virtual >>> host in Tomcat, and you can do whatever you want (e.g. single >>> virtual host) in httpd. > > Maybe i need to give a summary of the existing setup and how we use > it: tomcat runs on port 8080 apache runs on port 80 Got it: no surprises here. > Someone requests http://share.domain.tld. This request lands on > our apache server. Apache has to know where to send the > http://share.domain.tld request, so i assume a vhost will need to > tell apache where to send that request. Yes, but the default vhost will do just fine: all requests will go to the same vhost. > The web app is alfresco and i am not sure how to have alfresco > sniff out the request. Your way sounds the easiest but i am not > sure how to go about it. Can you share any examples? 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 some folks on the list who do and might reply here. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSOFymAAoJEBzwKT+lPKRYxRoP/iMNI1ueS99p2Jmb0qlRSMkb W50eBkReFvNGJZov9bEXmQGnZBQ+UpBVpczvhyWUos5Bhk+ra/2CRztdVssjTohU 8/rDwHpDF0qW1/tHhTMxGfrIH5Dn3Pr00vjFkMxlmuZKS5Ot4IwOF+VUa5sVdm0P tTsyGRquQmqi1WHr+ey5/5V6wHoq0EBjmVwdSTdUKiyCxQcfDDdgouhBiJ7td513 nBZvgo3Zx/ZHKnZkC2UrJP9Xu2bAxofogTcmVl9BOSVcUGVAD/YhzTO896zMitn4 4xOYZWIHrPzm9mU46RsCIne0mck2Xy5dA8Xe2PhJuC6CjjOJtI+qLaFJi95ESNih 3+6MQBEpzJGC8HmcVr+qZpw8bb7t4/UEJspAvXlA9fVoK4NBvyFq+Tlt3MiCaIMF fI1DBeyMTe6e5GjV4dIpq3JOxeb8X1NoF73aMdiVLtj/lSWPu0Kf7r5HVDjZc/Ch weRpgngEODzT1HwSXiE5Y+VbVjyQKqsQ72BKna4rmhLQkVe87Wf0JGZVHO6+3qLL f/xiipIi/PPGfTveHuQOeQCSACAjTUl52lz24SnDvFZuT/Yhy6gWuEvAG158cIh5 UkQHCNlJsr5ksiBwsGjHd6sjSd8d6+0uDWsbMzrpL8PjLrUtaWzfh4lJhYQ0SDCy uMzVJRrXJ5ZZMCHR7QTz =m8LV -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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 need to give a summary of the existing setup and how we use it: tomcat runs on port 8080 apache runs on port 80 Someone requests http://share.domain.tld. This request lands on our apache server. Apache has to know where to send the http://share.domain.tld request, so i assume a vhost will need to tell apache where to send that request. The web app is alfresco and i am not sure how to have alfresco sniff out the request. Your way sounds the easiest but i am not sure how to go about it. Can you share any examples? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
-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 >> >>> 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://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.domain1.tld and some will get to it >>> from http://share.domain2.tld. Can tomcat do this or should i >>> take a different approach? >> >> Assuming you get the various names registered in the appropriate >> DNS boxes, yes. Read the Tomcat doc and wiki, especially these >> bits: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html >> http://wiki.apache.org/tomcat/TomcatDevelopmentVirtualHosts >> >> You can also use a filter to forward requests to the desired URL: >> http://tuckey.org/urlrewrite/ > > >>> I would say that it would be helpful to know how your webapp >>> detects which "client" is being accessed. Are you sniffing that >>> from the URL in a single webapp, or are you configuring a >>> single webapp for each client (i.e. multiple webapps >>> concurrently deployed). >>> > > Not configuring a single app for each user. http://share.domain.tld > hits apache and apache should "forward" the connection to tomcat 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. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSNw4JAAoJEBzwKT+lPKRYucwQAITvXSYc8b2k4JySHaiJD469 GG/mQt3NlLiTKdfiZA+CZHwuZ5oa5jAQXyMXY8LOqyecDZKMioZFakNdrA61sdP3 yx5EQwjYidTE7oYJwk4YDcSDWie4zubyA05kSbRHk6+vUJNyR0X+TXKSmqL/0b+f Jz7bu1VuK/y4ZUg03pa7SqVxbOY+P+Yse0traiZoqcGZBWfN2nGIbpkQezJohmx6 k4sJNUGvJI92cimWPhyiI4nV9zYCf6HPc90GKYDA+HumNCnqdKNQWEp2Ybmf1vu4 biMLHQOzwg+9rLtM/0FwYz8YT7tLR7WIpQWYJqiI9UBQ3vyaUWpyjHVGF+rKbIJF jBoQxltHEOBZhFelRA1o2eqfOHp4DJtaxWbGh18ZRGb+BOyDN4Fj/YrnE2zxZGuM Vm5yXzxXlCcf04lO5XqTKoGfKh5P6cOaBnwCodPWJkKikVkS9Iva3tkmyE9eK5IJ 0EC/SAF6dL8c60pmBHAluYB4eA/9gumU0K65yx5sjDgHXXf1CPWVE2Flpnzm2m4F 2hqmETvrdLkeg7J6T0y3VJkN9hc0KKMAqwnfdtp0J7O9zChlbVgpYeQE9b/3f1V3 UM0MualN6iXG4MNhPRVyj/LvL+K/IjMQXWrrhaxvJhICTwXOLbBAwElsbUCpjcsv 1nK77XRwar7RQQmkdZjE =2/CS -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
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.0.3, you need to upgrade ASAP. > >> 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.domain1.tld and some will get to it from >> http://share.domain2.tld. Can tomcat do this or should i take a >> different approach? > > Assuming you get the various names registered in the appropriate > DNS boxes, yes. Read the Tomcat doc and wiki, especially these > bits: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html > http://wiki.apache.org/tomcat/TomcatDevelopmentVirtualHosts > > You can also use a filter to forward requests to the desired URL: > http://tuckey.org/urlrewrite/ >>I would say that it would be helpful to know how your webapp detects >>which "client" is being accessed. Are you sniffing that from the URL >>in a single webapp, or are you configuring a single webapp for each >>client (i.e. multiple webapps concurrently deployed). >> Not configuring a single app for each user. http://share.domain.tld hits apache and apache should "forward" the connection to tomcat >>If you are doing the former, then it shouldn't be tough to just sniff >>a different part of the URL to determine the client. If the latter, >>then you will either have to re-code your webapp to do URL-sniffing, >>or just deploy your webapps into individual s with separate >>appBase directories. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Multi-URL Access 1 Webapp
-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 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://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.domain1.tld and some will get to it from >> http://share.domain2.tld. Can tomcat do this or should i take a >> different approach? > > Assuming you get the various names registered in the appropriate > DNS boxes, yes. Read the Tomcat doc and wiki, especially these > bits: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html > http://wiki.apache.org/tomcat/TomcatDevelopmentVirtualHosts > > You can also use a filter to forward requests to the desired URL: > http://tuckey.org/urlrewrite/ +1 I would say that it would be helpful to know how your webapp detects which "client" is being accessed. Are you sniffing that from the URL in a single webapp, or are you configuring a single webapp for each client (i.e. multiple webapps concurrently deployed). If you are doing the former, then it shouldn't be tough to just sniff a different part of the URL to determine the client. If the latter, then you will either have to re-code your webapp to do URL-sniffing, or just deploy your webapps into individual s with separate appBase directories. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJSM3ttAAoJEBzwKT+lPKRYteQQAKK+2ww9wm5YtxST34SU7kW+ ppwzfY3bif1VNcpYW+H69my4vEFFiwJn6ZTx+GVLtL17445CmkXFh6nMtzLG2e6i 8CDo6ZJpeYbTVvIPyWzcLxDpmJfHVHZb9HZ0FV8aJK0QIxU7HxQGqzAKp8vn6eHw Y1R/z1wnhDm62ofYpgC4IQzB6St9U1AqoGdoBxtERrO6uR9g7mv6fehLhBvVbWis u7sIdfBYhk57mxCQojX9EZTLIsXPRBZ7+qXXLCZtYn9EigjOkD13XIZNT0Izrlqv WnXPMhEM9B16Q/taq53gWHP+zlOTpZydw5sIy+7UUoFWZMjAVxbm3f4l0qLyaLCu CA8NWM66xZ2fnic/+UUtL+QDvZEUSUTSAtoMcnt1zqaLDJJPR6FcxxGKa9n6Ppn1 ItF/bDGHgaYZfIr2uV3uEKrGEWCeOYGHz8O54DU7eNrz+Ck7B9Ilh+0v6a50wXMr mlLDdMmZ+Y/StmyfuylNJQlV1xx+zB8gvmtgnP1K6qMD+1lPqnYalwxnkSFkC4Fi qwpJVT+0QyG6lW2f/J00X75I+++25KBgLXGZKj3bOPu2nvyvGM6TszAR8ywL0S2k SpOrTjuzZulzW4bbIfQn+kjjp27akgJHwuLZrRgFsl/imQJt/VdXaY0FJQLCRlbx qj4L8ln4myDszCEwb/cw =Vuhq -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multi-URL Access 1 Webapp
> 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://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.domain1.tld and some will get to it from > http://share.domain2.tld. > Can tomcat do this or should i take a different approach? Assuming you get the various names registered in the appropriate DNS boxes, yes. Read the Tomcat doc and wiki, especially these bits: http://tomcat.apache.org/tomcat-7.0-doc/config/host.html http://wiki.apache.org/tomcat/TomcatDevelopmentVirtualHosts You can also use a filter to forward requests to the desired URL: http://tuckey.org/urlrewrite/ - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Multi-URL Access 1 Webapp
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.domain1.tld and some will get to it from http://share.domain2.tld. Can tomcat do this or should i take a different approach? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
