o***@yahoo.com
2007-02-05 20:39:41 UTC
Hi,
We are trying to configure IBM HTTP Server and our web application running on WebSphere application server. We are using the IBM Web Server Plug-in. The versions are the latest 6.0.2.x versions for all products.
The goal is to have the application servers behind the web servers, and the deployed web applications expose user-friendly urls to the public users.
We configured the user friendly URLs using mod_rewrite in IHS for INITIAL application access. For illustration, here are the configuration entries:
RewriteRule ^/$ /app/ [R]
RewriteRule ^/app/(.*)$ /webapp/public/$1 [PT]
RewriteRule ^/admin$ /admin/ [R]
RewriteRule ^/admin/(.*)$ /webapp/admin/$1 [PT]
This is because we have 2 Struts modules (public and admin) within one web application named webapp.
The problem with this configuration is that the web page served to the user still has all the application server URLs. For example, some link on the web page will look like:
http://www.example.com/webapp/public/some_link.do
, instead of:
http://www.example.com/app/some_link.do
For this, in Apache world, there is mod_proxy_html. This module would replace the 'old' URLs (/webapp/public/) with the 'new' ones (/app/). However, for this to work, one needs to use the other Apache mod_proxy modules (mod_proxy, mod_proxy_http).
In one of the postings, someone mentioned that mod_proxy modules should not be used, which makes sense, since that's the role of the IBM Web Server Plug-in.
Has anyone here had any experience with this type of configuration?
Thanks for the help.
We are trying to configure IBM HTTP Server and our web application running on WebSphere application server. We are using the IBM Web Server Plug-in. The versions are the latest 6.0.2.x versions for all products.
The goal is to have the application servers behind the web servers, and the deployed web applications expose user-friendly urls to the public users.
We configured the user friendly URLs using mod_rewrite in IHS for INITIAL application access. For illustration, here are the configuration entries:
RewriteRule ^/$ /app/ [R]
RewriteRule ^/app/(.*)$ /webapp/public/$1 [PT]
RewriteRule ^/admin$ /admin/ [R]
RewriteRule ^/admin/(.*)$ /webapp/admin/$1 [PT]
This is because we have 2 Struts modules (public and admin) within one web application named webapp.
The problem with this configuration is that the web page served to the user still has all the application server URLs. For example, some link on the web page will look like:
http://www.example.com/webapp/public/some_link.do
, instead of:
http://www.example.com/app/some_link.do
For this, in Apache world, there is mod_proxy_html. This module would replace the 'old' URLs (/webapp/public/) with the 'new' ones (/app/). However, for this to work, one needs to use the other Apache mod_proxy modules (mod_proxy, mod_proxy_http).
In one of the postings, someone mentioned that mod_proxy modules should not be used, which makes sense, since that's the role of the IBM Web Server Plug-in.
Has anyone here had any experience with this type of configuration?
Thanks for the help.