| Author |
redirecting request on IBM Httpd2
|
|
|
| How do I redirect all request to port 80 to WebSphere's 9443? I only want to server up the site on default_host ssl.
| |
| Sunit Patke 2006-03-15, 5:57 pm |
| If I understand you correctly you want to send all HTTP traffic to HTTPS for
a WAS web application.
You have a websphere application listening on port 9443. Install IBM HTTP
Server with WAS plug-in. Make sure the host alias for you webapp has port
443 but not 80. Generate the plugin-cfg.xml file in WAS adminconsole and
make sure it is being used by IHS.
In httpd.conf create a Rewrite rule in VirtualHost with port 80 to forward
all traffic to HTTPS
Sunit
<shedrick.hollaway@navy.mil> wrote in message
news:1776277466.1142436890613.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> How do I redirect all request to port 80 to WebSphere's 9443? I only want
> to server up the site on default_host ssl.
| |
|
| > If I understand you correctly you want to send all
> HTTP traffic to HTTPS for
> a WAS web application.
This is exactly what I want to do.
> You have a websphere application listening on port
> 9443. Install IBM HTTP
> Server with WAS plug-in. Make sure the host alias for
> you webapp has port
> 443 but not 80. Generate the plugin-cfg.xml file in
> WAS adminconsole and
> make sure it is being used by IHS.
I have done this and tested to verify.
> In httpd.conf create a Rewrite rule in VirtualHost
> with port 80 to forward
> all traffic to HTTPS
>
> Sunit
The setup of the VirtualHost and redirection is what I am unsure of doing. And I was wondering if anyone had experience with doing this setup.
| |
| Sunit Patke 2006-03-15, 5:57 pm |
| Which version of IHS?
Sunit
<shedrick.hollaway@navy.mil> wrote in message
news:1354520550.1142443254074.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
>
> This is exactly what I want to do.
>
>
> I have done this and tested to verify.
>
>
> The setup of the VirtualHost and redirection is what I am unsure of doing.
> And I was wondering if anyone had experience with doing this setup.
| |
|
|
|
|
|
| > <VirtualHost yourserver:80>
> RewriteEngine on
> RewriteRule ^/(.*) https://your.server.name/$1 [P]
> </VirtualHost>
>
> <VirtualHost yourserver:443>
> ...other config directives
> </VirtualHost>
>
This did help but it leads to an issue with mod_ibm_ssl which I have not found an answer. This posting should clarify things some.
http://www-128.ibm.com/developerwor...9&q=Proxy#98698
<SNIP>
IHS does not use mod_ssl.so, it has its own SSL implementation using
mod_ibm_ssl.so which does not support the SSLProxyEngine directive.
Actually I would be iterested to know what your (or anyone elses)
requirements are for this functon - i.e. to be able to run SSL to
the backend server for Reverse Proxy configurations:
client --> HTTP --> ReverseProxy --> HTTPS --> Origin Server
or
client --> HTTPS --> ReverseProxy --> HTTPS --> Origin Server
</SNIP>
This is the end scenario I am seeking after.
| |
|
| This looks to be working.
<VirtualHost *:80>
RewriteEngine on
RewriteRule ^/(.*) https://<hostname>/$1 [R]
</VirtualHost>
<VirtualHost *:443>
SSLEnable
SSLClientAuth None
</VirtualHost>
SSLDisable
KeyFile _path_to_your_keyfile #e.g. /etc/key.kdb
SSLStashfile _path_to_your_pwd_stash #e.g. /etc/key.sth
| |
| Sunit Patke 2006-03-21, 3:45 am |
| With WebSphere Application Server we do not use proxy implementation of
Apache bu rather we use WAS plug-in.
Sunit
<shedrick.hollaway@navy.mil> wrote in message
news:1519465230.1142697114182.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> This did help but it leads to an issue with mod_ibm_ssl which I have not
> found an answer. This posting should clarify things some.
> http://www-128.ibm.com/developerwor...9&q=Proxy#98698
> <SNIP>
> IHS does not use mod_ssl.so, it has its own SSL implementation using
> mod_ibm_ssl.so which does not support the SSLProxyEngine directive.
>
> Actually I would be iterested to know what your (or anyone elses)
> requirements are for this functon - i.e. to be able to run SSL to
> the backend server for Reverse Proxy configurations:
>
> client --> HTTP --> ReverseProxy --> HTTPS --> Origin Server
> or
> client --> HTTPS --> ReverseProxy --> HTTPS --> Origin Server
> </SNIP>
>
> This is the end scenario I am seeking after.
>
>
>
>
|
|
|
|