Hello Edge Server Forum readers,

Could someone pls advise if multiple (more than one)  proxy directives could
be specified
in Reverse proxy configuration file (ibmproxy.conf)  for processing http (or
ftp) protocols
and passing the requests to more than one content servers (Web Application
ervers)?
Can you give an example?

Any advise will be much appreciated.
Regards, Nick Dakoronias

PS:
I have used the following input as guideline:
Abstract for Poxy Directive from Edge Server v2.0 Admin guide:
Proxy directive Format

Proxy protocol *

This directive can also be used to pass the request to a remote proxy
server, also known as reverse proxy.

For example, the following directive causes all

requests to be forwarded to the designated URL:

Proxy /* http://proxy.server.name/*

For a secure reverse proxy server, use the following directive:

Proxy /* https://proxy.server.name/

------------------------------------------------



In a reverse proxy configuration, a proxy server is placed between one or

more content servers and the Internet. It accepts requests from Internet
clients

for content stored on the proxy server's home site. The proxy server appears

to the client to be the origin (content) server; the client is not aware
that the

request has been sent to another server.

To configure the Caching Proxy as a reverse proxy, specify the content
server

to which requests are forwarded. The following example procedure edits the

configuration file to set up the Caching Proxy as a reverse proxy for the

content server at www.mycontentserver.com:

[ Post a follow-up to this message ]

Nick Dakoronias wrote:
> Hello Edge Server Forum readers,
>
> Could someone pls advise if multiple (more than one)  proxy directives cou
ld
> be specified
> in Reverse proxy configuration file (ibmproxy.conf)  for processing http (
or
> ftp) protocols
> and passing the requests to more than one content servers (Web Application
> ervers)?
> Can you give an example?
>
> Any advise will be much appreciated.
> Regards, Nick Dakoronias
>
> PS:
> I have used the following input as guideline:
> Abstract for Poxy Directive from Edge Server v2.0 Admin guide:
> Proxy directive Format
>
> Proxy protocol *
>
> This directive can also be used to pass the request to a remote proxy
> server, also known as reverse proxy.
>
> For example, the following directive causes all
>
> requests to be forwarded to the designated URL:
>
> Proxy /* http://proxy.server.name/*
>
> For a secure reverse proxy server, use the following directive:
>
> Proxy /* https://proxy.server.name/
>
> ------------------------------------------------
>
>
>
> In a reverse proxy configuration, a proxy server is placed between one or
>
> more content servers and the Internet. It accepts requests from Internet
> clients
>
> for content stored on the proxy server's home site. The proxy server appea
rs
>
> to the client to be the origin (content) server; the client is not aware
> that the
>
> request has been sent to another server.
>
> To configure the Caching Proxy as a reverse proxy, specify the content
> server
>
> to which requests are forwarded. The following example procedure edits the
>
> configuration file to set up the Caching Proxy as a reverse proxy for the
>
> content server at www.mycontentserver.com:
>

If I understand you correctly, sure.  We proxy to several different servers.
you can do this based simply on the URL paths, on the hostnames, or on a
combination.  It's particularly nice for name-based virtual hosts.  For exam
ple:

# DNS hostname-specific
Proxy      /webapp/* http://server1/webapp/* dnsname1
Proxy      /webapp/* http://server2/webapp/* dnsname2
# no hostname (for all hostnames)
Proxy      /webapp2/* http://server1/webapp2/*
# default for a particular hostname
Proxy      /* http://server2/* dnsname1

What you can't do, and I don't think this is what you were asking, is have a
single proxy server route to two different (redundant) app servers for the
exact same URL.
--
Doug

[ Post a follow-up to this message ]

Doug,
Your response was quite clear.
Thanks.

"Doug Breaux" <doug@clearlake.ibm.com> wrote in message
news:cisg4i$35lm$1@news.boulder.ibm.com...
> Nick Dakoronias wrote: 
could[vbcol=seagreen] 
(or[vbcol=seagreen] 
Application[vbcol=seagreen] 
or[vbcol=seagreen] 
appears[vbcol=seagreen] 
the[vbcol=seagreen] 
the[vbcol=seagreen] 
>
> If I understand you correctly, sure.  We proxy to several different
servers.
> you can do this based simply on the URL paths, on the hostnames, or on a
> combination.  It's particularly nice for name-based virtual hosts.  For
example:
>
> # DNS hostname-specific
> Proxy      /webapp/* http://server1/webapp/* dnsname1
> Proxy      /webapp/* http://server2/webapp/* dnsname2
> # no hostname (for all hostnames)
> Proxy      /webapp2/* http://server1/webapp2/*
> # default for a particular hostname
> Proxy      /* http://server2/* dnsname1
>
> What you can't do, and I don't think this is what you were asking, is have
a
> single proxy server route to two different (redundant) app servers for the
> exact same URL.
> --
> Doug

[ Post a follow-up to this message ]