WebSphere Edge Server - Proxy setup and IHS redirects

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Edge Server > January 2004 > Proxy setup and IHS redirects





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 Proxy setup and IHS redirects
Doug

2004-01-19, 3:02 pm

Forgive me if this is the wrong newsgroup or if this information is readily
available in a manual somewhere. I'm not really sure where to start
looking.

I've got the following ibmproxy.conf line to (reverse) proxy external
requests to an internal IHS/WebSphere server:

Proxy /id/* http://<internal_server>/id/*

Where my internal server has a WebSphere application with a context root of
"/id/lookup/".

Requests to http://<cache_server/id/lookup/ work as expected. However,
requests to http://<cache_server>/id/lookup without the trailing slash get
redirected (I think by IHS) to http://<internal_server>/id/lookup/ (with the
trailing slash, but with the internal server name), which is obviously not
good.

Anyone know a way around this? Or have I needlessly complicated something
that has a simpler solution? Thanks.

Doug


Klaus Johannes Rusch

2004-01-19, 3:02 pm

Doug wrote:
quote:

> Forgive me if this is the wrong newsgroup or if this information is readily
> available in a manual somewhere. I'm not really sure where to start
> looking.
>
> I've got the following ibmproxy.conf line to (reverse) proxy external
> requests to an internal IHS/WebSphere server:
>
> Proxy /id/* http://<internal_server>/id/*
>
> Where my internal server has a WebSphere application with a context root of
> "/id/lookup/".
>
> Requests to http://<cache_server/id/lookup/ work as expected. However,
> requests to http://<cache_server>/id/lookup without the trailing slash get
> redirected (I think by IHS) to http://<internal_server>/id/lookup/ (with the
> trailing slash, but with the internal server name), which is obviously not
> good.
>
> Anyone know a way around this? Or have I needlessly complicated something
> that has a simpler solution? Thanks.



The internal_server needs to use a server name that is the same as the external
hostname, i.e. if your server is www.example.com, then the host name directive
on the backend internal_server should say www.example.com, not internal_server.
--
Klaus Johannes Rusch
KlausRusch@atmedia.net
http://www.atmedia.net/KlausRusch/


Doug

2004-01-19, 3:02 pm


"Klaus Johannes Rusch" <KlausRusch@atmedia.net> wrote in message
news:3E9887CB.B0319FAB@atmedia.net...
quote:

> Doug wrote:
>
readily[QUOTE][color=darkred]
of[QUOTE][color=darkred]
get[QUOTE][color=darkred]
the[QUOTE][color=darkred]
not[QUOTE][color=darkred]
something[QUOTE][color=darkred]
>
> The internal_server needs to use a server name that is the same as the


external
quote:

> hostname, i.e. if your server is www.example.com, then the host name


directive
quote:

> on the backend internal_server should say www.example.com, not


internal_server.

Hmmmm... I could see where that would be one way to solve my problem, but
the <internal_server> is on a whole different subnet (behind a firewall), so
it can't use the name of the <cache_server>. Or am I misunderstanding you?

Doug


Adrian

2004-01-19, 3:02 pm

What Klaus is suggesting you do is change the ServerName parameter in
the IHS config file to be <cache_server>. This does not mean
reconfiguring your hostname - just the IHS conf.

Doug wrote:
quote:

> "Klaus Johannes Rusch" <KlausRusch@atmedia.net> wrote in message
> news:3E9887CB.B0319FAB@atmedia.net...
>
>
> readily
>
>
> of
>
>
> get
>
>
> the
>
>
> not
>
>
> something
>
>
> external
>
>
> directive
>
>
> internal_server.
>
> Hmmmm... I could see where that would be one way to solve my problem, but
> the <internal_server> is on a whole different subnet (behind a firewall), so
> it can't use the name of the <cache_server>. Or am I misunderstanding you?
>
> Doug
>
>



Doug

2004-01-19, 3:02 pm

That's what I thought, but I thought IHS wouldn't allow a ServerName that it
really isn't bound to.

Also, if that same IHS is used for multiple server names (which is fairly
likely), this wouldn't solve everything.

"Adrian" <barftud@redbrick.dcu.ie> wrote in message
news:b7eo7g$3s7s$1@news.boulder.ibm.com...
quote:

> What Klaus is suggesting you do is change the ServerName parameter in
> the IHS config file to be <cache_server>. This does not mean
> reconfiguring your hostname - just the IHS conf.
>
> Doug wrote:
root[QUOTE][color=darkred]
(with[QUOTE][color=darkred]
but[QUOTE][color=darkred]
firewall), so[QUOTE][color=darkred]
you?[QUOTE][color=darkred]
>




Adrian

2004-01-19, 3:02 pm

For your first point, IHS definitely lets you set ServerName to a
hostname other than it's DNS name... that's what it's there for:

http://httpd.apache.org/docs-2.0/mo...html#servername

For the second point, that's what Virtual Hosts are for:

http://httpd.apache.org/docs-2.0/vhosts/


Doug wrote:
quote:

> That's what I thought, but I thought IHS wouldn't allow a ServerName that it
> really isn't bound to.
>
> Also, if that same IHS is used for multiple server names (which is fairly
> likely), this wouldn't solve everything.
>
> "Adrian" <barftud@redbrick.dcu.ie> wrote in message
> news:b7eo7g$3s7s$1@news.boulder.ibm.com...
>
> root
>
> (with
>
> but
>
>
> firewall), so
>
>
> you?
>
>
>



Doug

2004-01-19, 3:02 pm

Replies inline...

"Adrian" <barftud@redbrick.dcu.ie> wrote in message
news:b7gu82$3jo2$1@news.boulder.ibm.com...
quote:

> For your first point, IHS definitely lets you set ServerName to a
> hostname other than it's DNS name... that's what it's there for:
>
> http://httpd.apache.org/docs-2.0/mo...html#servername



Again, I realize that. I just thought it had to be a name for which the IP
address did exist somewhere on the box (even if it wasn't its primary DNS
name). i.e. I thought it couldn't give www.yahoo.com to my server if its IP
address wasn't configured on one of the server's network (or loopback)
adapters.
quote:

> For the second point, that's what Virtual Hosts are for:
>
> http://httpd.apache.org/docs-2.0/vhosts/



Yes, but I'm trying to avoid having to create multiple names or IP addresses
just for this redirect. I don't need them for anything else. I already
have to have them on the Proxy server, but there's no (other) reason I
should need them on the proxied (application) servers.
quote:

>
> Doug wrote:
that it[QUOTE][color=darkred]
fairly[QUOTE][color=darkred]
However,[QUOTE][color=darkred]
slash[QUOTE][color=darkred]
obviously[QUOTE][color=darkred]
>




Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com