|
Home > Archive > WebSphere Edge Server > January 2004 > Reverse Proxy and Portal 4.2
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 |
Reverse Proxy and Portal 4.2
|
|
| Andre Venancio 2004-01-19, 3:03 pm |
| Any help will be appreciated
Our customer is running WPS 4.2 in an AIX 5.1 box, and WES 5.0 in
another AIX 5.1 box.
He had installed and configured WPS 4.2 previously, and it is working
fine.
Now, he installed WebSphere Edge Server 5.0 (WES) in a separate box,
and he wants to use this box as a reverse proxy for the Portal site.
He configured the proxy server to redirect all requests to the
portal server, and it is working fine except for the Login link:
it is being hardcoded using the portal server hostname.
For example, the WPS server hostname is "portal" and the WES hostname
is "proxy". After configuring the reverse proxy, the customer
uses the following URL in the browser:
http://proxy.domain.com/wps/portal
In the resulting page, all links are correct except the Login link,
which reads:
http://portal.domain.com/wps/portal/.scr/Login
Is it possible to prevent WPS from hardcoding the Login link, so it will
work fine in the reverse proxy scenario?
Do you recommend a different approach for a reverse proxy scenario?
Regards.
André Barros Venāncio
| |
|
| > Is it possible to prevent WPS from hardcoding the Login link, so it willquote:
> work fine in the reverse proxy scenario?
Yes, we did it. There is a properties or config file where you can specify
the host and port to use. I can't remember exactly, but the InfoCenter might
help.
|
|
|
|
|