|
Home > Archive > WebSphere HTTP Server > April 2004 > apache mod_ssl = problems with WAS-plugin
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
apache mod_ssl = problems with WAS-plugin
|
|
| glunix 2004-04-07, 2:33 pm |
| I have some difficulties restricting applications to ssl/https.
We have a dedicated apache on a linux-box, which connects to an
appserver to serve dynamic content. (Nearly) everything works. The
webserver is an apache 1.3.xx out of the box (debian woody) using
mod_ssl. The appservers are running on Linux SLES and/or Solaris.
Although only Port :80 is configured in the appserver and the plugin, it
works as well when contacting the webserver on :443/https.
But now I have to restrict access to some application to https and I'am
unable to do so. When I change the ports in the plugin-cfg.xml to :443,
my request are ignored by the plugin -> 404
When I trace the plugin, the log shows that every request is tagged with
port :80, even if it is served from :443 by the webserver.
Any suggestions?
Thanks!
--
posted via MFF : http://www.MainFrameForum.com - USENET Gateway
| |
| Aaron W Morris 2004-04-07, 3:33 pm |
|
glunix wrote:
> I have some difficulties restricting applications to ssl/https.
>
> We have a dedicated apache on a linux-box, which connects to an
> appserver to serve dynamic content. (Nearly) everything works. The
> webserver is an apache 1.3.xx out of the box (debian woody) using
> mod_ssl. The appservers are running on Linux SLES and/or Solaris.
>
> Although only Port :80 is configured in the appserver and the plugin, it
> works as well when contacting the webserver on :443/https.
>
> But now I have to restrict access to some application to https and I'am
> unable to do so. When I change the ports in the plugin-cfg.xml to :443,
> my request are ignored by the plugin -> 404
>
> When I trace the plugin, the log shows that every request is tagged with
> port :80, even if it is served from :443 by the webserver.
>
> Any suggestions?
>
> Thanks!
>
>
>
> --
> posted via MFF : http://www.MainFrameForum.com - USENET Gateway
You need to add :443 to the WebSphere virtual host on the app servers.
Otherwise, the app server will not respond to the requests. A restart
of the app server will be required, of course.
--
Aaron W Morris <aaronmorris@mindspring.com> (decep)
| |
| glunix 2004-04-08, 2:33 am |
| Yes, that is what is written in the docs.
But the Applicationserver responds to all Request, http & https - but
only http is configured in the appserver and the plugin!
Every Request either http or https is treated as http:80 according to
the plugin-trace and the results in the browser of course. THIS make it
impossible to restrict access for some applications.
--
posted via MFF : http://www.MainFrameForum.com - USENET Gateway
|
|
|
|
|