Comments on: Previewing Content on Load Balanced Web Servers http://coreygilmore.com/blog/2007/08/10/previewing-content-on-load-balanced-web-servers/ Mon, 06 Feb 2012 11:13:39 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Corey http://coreygilmore.com/blog/2007/08/10/previewing-content-on-load-balanced-web-servers/comment-page-1/#comment-216 Corey Mon, 17 Sep 2007 04:25:59 +0000 http://coreygilmore.com/blog/2007/08/10/previewing-content-on-load-balanced-web-servers/#comment-216 I'd definitely prefer a solution like that, unfortunately I'm not in a position to force that type of change (or at least it's not worth the fight given the other issues I'd rather see fixed). The other issue will be any form that uses absolute URLs and pages that redirect you. I'd definitely prefer a solution like that, unfortunately I'm not in a position to force that type of change (or at least it's not worth the fight given the other issues I'd rather see fixed). The other issue will be any form that uses absolute URLs and pages that redirect you.

]]> By: Brian Blood http://coreygilmore.com/blog/2007/08/10/previewing-content-on-load-balanced-web-servers/comment-page-1/#comment-83 Brian Blood Tue, 28 Aug 2007 01:06:54 +0000 http://coreygilmore.com/blog/2007/08/10/previewing-content-on-load-balanced-web-servers/#comment-83 You can also go a different route. Create Single service content rules in the load balancer that map a specific port to only a single server. In the NLB, the rules would be: port 80 could go to servers A, B, C or D port 8001 would go to Server A port 8002 would go to Server B etc. etc... On the server side you won't have to change anything, as the NLB should translate the ports internally from 8001 to port 80. This way you can still use full host names from the outside, yet be sure that you are only accessing content on a specific server like so: http://www.domain.com:8001/ You can also go a different route. Create Single service content rules in the load balancer that map a specific port to only a single server.

In the NLB, the rules would be:
port 80 could go to servers A, B, C or D
port 8001 would go to Server A
port 8002 would go to Server B
etc. etc…

On the server side you won't have to change anything, as the NLB should translate the ports internally from 8001 to port 80.

This way you can still use full host names from the outside, yet be sure that you are only accessing content on a specific server like so:

http://www.domain.com:8001/

]]>