I don't want to go into semantics but what you name "Web Front End " is
actually a reverse-proxy.
I would therfore use a real one instead of IIS (ISA, SQUID, even Apache can
do)
If you want to stick to an IIS-based solution, maybe this ASP.Net code can
help:
http://www.codeproject.com/KB/web-security/HTTPReverseProxy.aspx
KR,
Marf
"Hadi Teo" <haditeo.mail.DeleteThis@gmail.com> wrote in message
news:C89ADF6F-A28D-464C-AD25-6D0E94ADB17D@microsoft.com...
> Hi,
>
> I have the following architecture :
>
> Client Browser -> Web Front End -> Firewall -> Web Application -> Database
> Server
>
> I have an issue in the Web Front End. Basically i have installed IIS in
> the
> Web Front End machine.
>
> I would like to know what are the configurations for IIS to route all the
> HTTP traffic from client browser to the Web Application through the
> firewall?
> The firewall will drop all the connections NOT originated from Web Front
> End,
> that is why i placed the Web Front End to act as a gateway. I would like
> to
> know the IIS configuration to act as a gateway.
>
> In my experiment, i have configured a default website and then placed a
> Response.Redirect command to route the traffic. But i have analyzed that
> Response.Redirect will just give the Web App IP to client browser and then
> the client browser connect directly to the Web App without going through
> the
> Web Front End.
>
> Thanks for your reply.
>
> Regards
>
> Hadi Teo.