Setting up a basic revers proxy for a windows web application


Has anyone seen someone post a basic example on how to use KEMP as a standard revers proxy for a IIS website or web application? I see tones of stuff or Lync and Exchange but nothing on a basic IIS site.

1 comment

Christian Scheller Official comment


using a KEMP Loadmaster as a reverse proxy for an IIS application is a standard scenario.

In general, you should consider using Layer 7 based services instead of Layer 4 since Layer 7 gives you the opportunity to modify the HTTP stream according to your needs (Header replacements, content rules...). Eventually you have the option to choose between a transparent- or non-transparent deployment.

Transparency means that the Client-IP address is NATted to the Real Server, which in turn would respond right back to the client, so the server's default Gateway needs to be set to the Loadmaster to avoid asynchronous routing. The IP would either be the LMs system IP or the VIP. In latter case the Option "Use Address for Server NAT" could be set to mask the return packets with the VIP.

The non-Transparent mode is usually the mode of choice for most users. The real server will always "see" the Loadmasters IP address as the senders address. Applications like Exchange for instance are capable of extracting the oroginal senders IP address from the HTTP headers to identify users.

If your interest in our product is of a commercial nature, I would suggest asking for a product demo and/or a PoC.


Thanks and Best Regards