ProxyPassReverse IIS 6.0 windows server 2003 How?

Hi Guys
I am a newbi to IIS.
Our customer is using IIS 6.0 on Windows server 2003 machine as the front
end .
However part of the java scripts needed to be downloaded by the clients
(Browsers) are from different site.
This may initiate on the client side a security event (browser ask if it’s
valid to download from that address and user may block it).

The common solution is proxyPassReverse – which is done on server side so
client is not aware of the redirection and all addresses seems to be from/to
the same origin.

The functionality needed (ProxyPassReverse) is as followed :
I am using the appache example since it very easy to understand (imaginary
addresses).

http://www.localserver.com/call = The IIS server
http://100.100.170.32:80/ = The other server

setup for proxyPassReverse using the apache mod_proxy.so module (httpd.conf
file)

# Pass the call from http://www.localserver.com/call to http://
100.100.170.32:80
ProxyPass /call/ http://100.100.170.32:80

# Handle any redirects that http:// 100.100.170.32:80 might respond with
ProxyPassReverse http://100.100.170.32:80 /call/

So for example if one is addressing http://www. localserver.com/call
It will be redirect to http://100.100.170.32:80/call
And when the http://100.100.170.32:80/call redirect to let’s say
http://100.100.170.32:80/abc/def/.....
Apache will redirect it to client and it would seem as
http://www.localserver.com/call/abc/def/ …..

As far as I know IIS does not directly support such functionality- Am i
correct?
The question is how can I (if at all) do it using the IIS (maybe installing
some add in or third party tool that work with the IIS since customer request
was to keep IIS as the server (Not to replace it with appache for example).

Thanks in advance & regards
Yuval

Re: ProxyPassReverse IIS 6.0 windows server 2003 How?

"yuvalyo" wrote in message
news:E3B149D5-8D8B-4FEF-A112-E684C8B3BA9D@microsoft.com...
> Hi Guys
> I am a newbi to IIS.
> Our customer is using IIS 6.0 on Windows server 2003 machine as the front
> end .
> However part of the java scripts needed to be downloaded by the clients
> (Browsers) are from different site.
> This may initiate on the client side a security event (browser ask if it's
> valid to download from that address and user may block it).
>

Which browsers do that?


--
Anthony Jones - MVP ASP/ASP.NET

Re: ProxyPassReverse IIS 6.0 windows server 2003 How?

Hi Yuval,

You should find that ISAPI Rewrite will do what you need done below,
http://www.isapirewrite.com. It can be added as an ISAPI Filter on the site
or globally at the server level as an ISAPI Filter. The rules are
configured through an httpd.ini file at the root of the site and it uses
regex. I have found their forums to be great at answering questions to help
get you started.

--
Rick Barber

http://www.orcsweb.com
Managed Complex Hosting
#1 in Service and Support

"yuvalyo" wrote in message
news:E3B149D5-8D8B-4FEF-A112-E684C8B3BA9D@microsoft.com...
> Hi Guys
> I am a newbi to IIS.
> Our customer is using IIS 6.0 on Windows server 2003 machine as the front
> end .
> However part of the java scripts needed to be downloaded by the clients
> (Browsers) are from different site.
> This may initiate on the client side a security event (browser ask if it's
> valid to download from that address and user may block it).
>
> The common solution is proxyPassReverse - which is done on server side so
> client is not aware of the redirection and all addresses seems to be
> from/to
> the same origin.
>
> The functionality needed (ProxyPassReverse) is as followed :
> I am using the appache example since it very easy to understand (imaginary
> addresses).
>
> http://www.localserver.com/call = The IIS server
> http://100.100.170.32:80/ = The other server
>
> setup for proxyPassReverse using the apache mod_proxy.so module
> (httpd.conf
> file)
>
> # Pass the call from http://www.localserver.com/call to http://
> 100.100.170.32:80
> ProxyPass /call/ http://100.100.170.32:80
>
> # Handle any redirects that http:// 100.100.170.32:80 might respond with
> ProxyPassReverse http://100.100.170.32:80 /call/
>
> So for example if one is addressing http://www. localserver.com/call
> It will be redirect to http://100.100.170.32:80/call
> And when the http://100.100.170.32:80/call redirect to let's say
> http://100.100.170.32:80/abc/def/.....
> Apache will redirect it to client and it would seem as
> http://www.localserver.com/call/abc/def/ ...
>
> As far as I know IIS does not directly support such functionality- Am i
> correct?
> The question is how can I (if at all) do it using the IIS (maybe
> installing
> some add in or third party tool that work with the IIS since customer
> request
> was to keep IIS as the server (Not to replace it with appache for
> example).
>
> Thanks in advance & regards
> Yuval

Re: ProxyPassReverse IIS 6.0 windows server 2003 How?

On Nov 7, 1:47 am, yuvalyo wrote:
> Hi Guys
> I am a newbi to IIS.
> Our customer is using IIS 6.0 on Windows server 2003 machine as the front
> end .
> However part of the java scripts needed to be downloaded by the clients
> (Browsers) are from different site.
> This may initiate on the client side a security event (browser ask if it's
> valid to download from that address and user may block it).
>
> The common solution is proxyPassReverse - which is done on server side so
> client is not aware of the redirection and all addresses seems to be from/to
> the same origin.
>
> The functionality needed (ProxyPassReverse) is as followed :
> I am using the appache example since it very easy to understand (imaginary
> addresses).
>
> http://www.localserver.com/call= The IIS serverhttp://100.100.170.32:80/ = The other server
>
> setup for proxyPassReverse using the apache mod_proxy.so module (httpd.conf
> file)
>
> # Pass the call fromhttp://www.localserver.com/call to http://
> 100.100.170.32:80
> ProxyPass /call/ http://100.100.170.32:80
>
> # Handle any redirects that http:// 100.100.170.32:80 might respond with
> ProxyPassReverse http://100.100.170.32:80 /call/
>
> So for example if one is addressinghttp://www. localserver.com/call
> It will be redirect tohttp://100.100.170.32:80/call
> And when thehttp://100.100.170.32:80/call redirect to let's sayhttp://100.100.170.32:80/abc/def/.....
> Apache will redirect it to client and it would seem ashttp://www.localserver.com/call/abc/def/.....
>
> As far as I know IIS does not directly support such functionality- Am i
> correct?
> The question is how can I (if at all) do it using the IIS (maybe installing
> some add in or third party tool that work with the IIS since customer request
> was to keep IIS as the server (Not to replace it with appache for example).
>
> Thanks in advance & regards
> Yuval



IIS directly supports such functionality as much as Apache. The
question is whether you have the correct extensibility module
installed.

Apache comes pre-bundled with 3rd party software like mod_rewrite and
mod_proxy that you know about. IIS comes clean and not bundled with
3rd party software, but you can use modules like ISAPI Rewrite to
achieve similar functionality as mod_rewrite and mod_proxy on IIS.

It sounds like you have another application running on a different
server, and you want to expose that application using the same URL
namespace of the front-end IIS web server. Thus, you want the front-
end to reverse proxy resources from that other server.

Trying to share one URL namespace with multiple servers is best
accomplished by a real proxy server. Is there any particular reason
you want to use the poor man's proxy approach?


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//