|
Home > Archive > WebSphere Application Server > July 2007 > Websphere 6 and HTTP forwards.
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 |
Websphere 6 and HTTP forwards.
|
|
|
| Hi,
I'm running a websphere 6 application server here which has its own domain. However, I wish to use a separate domain to forward to the server with a HTTP 301 redirect.
Is there a setting on the Websphere application server to display the original (i.e. the domain which is forwarded from) domain in the web address box in the browser as opposed to the server URL?
Thanks,
Mike.
| |
|
| > I'm running a websphere 6 application server here which has its own
> domain. However, I wish to use a separate domain to forward to the server
> with a HTTP 301 redirect.
>
> Is there a setting on the Websphere application server to display the
> original (i.e. the domain which is forwarded from) domain in the web
> address box in the browser as opposed to the server URL?
I don't understand what you're requesting.
You can arrange a redirect by installing IBM HTTP Server (and its web server
plug-in) as facade to your WebSphere application and add a directive in
httpd.conf.
But you say you want to see the original address in the browser. And in this
case, I'd say you don't want a redirect but a virtual host.
Can you clarify ?
| |
| Doug Breaux 2007-07-26, 7:21 pm |
| michael_palfrey@natbrit.com wrote:
> Hi,
>
> I'm running a websphere 6 application server here which has its own domain. However, I wish to use a separate domain to forward to the server with a HTTP 301 redirect.
>
> Is there a setting on the Websphere application server to display the original (i.e. the domain which is forwarded from) domain in the web address box in the browser as opposed to the server URL?
>
> Thanks,
>
> Mike.
>
If you really mean a 301 redirect, then what you're asking isn't possible with
any server. With a 301, the server tells the browser to send a second request
asking for an entirely different URL.
As Ben said, perhaps you can clarify exactly what you want to happen.
--
Doug
| |
|
| Hi,
Apologies for the ambiguity in my question.
Essentially what I want to happen is that someone accesses domainA, this then will forward to domainB yet in the address field in their browser will show domainA at all times- this could be obtained through using a frame but I was hoping that another solu
tion could be found.
Thanks for the responses so far.
Mike.
| |
|
| Beside the frame trick, there is no means to make the browser tell the URL
of a different web site than the one you're viewing. Notice that the frame
trick is not perfect either, as it causes problems with bookmarks and
refresh of pages for example.
What you could do is have a proxy forward the traffic to domainB / serverB
and have this topology: browser --(connect)--> server A --(proxy)--> server
B. But that's a different topology, involving more than just a WebSphere
configuration.
| |
| Doug Breaux 2007-07-27, 1:24 pm |
| michael_palfrey@natbrit.com wrote:
> Hi,
>
> Apologies for the ambiguity in my question.
>
> Essentially what I want to happen is that someone accesses domainA, this then will forward to domainB yet in the address field in their browser will show domainA at all times- this could be obtained through using a frame but I was hoping that another so
lution could be found.
>
> Thanks for the responses so far.
>
> Mike.
Yes, that's more like a proxy, although you'll have to configure the proxy a
certain way to completely hide the server's real domain. i.e. to make all
self-referential links and form submissions (including any you have in
JavaScript) be translated to the hostname you want the user to see. That or
make sure your code explicitly uses the original hostname for all
self-referential links and form submissions.
Is there any reason why the server can't be configured to respond natively on
the desired hostname?
--
Doug
|
|
|
|
|