Observations and explanations

)irsW oI all, ,'P running Py :eb serYers on 192.168.0.7 and 192.168.0.8 as Yisible aboYe—yeW, , access WheP aW Whe address 192.168.0.6. This is because your (clienW/browser) requesW(s) must be made to mound, which fetches the response from the Web servers mentioned in pound.cfg and reWurns iW. Sure, in our WesW seW-uS, you can direcWly access Whe websiWes aW 192.168.0.7 or .8, buW in real-world siWuaWions, you'd firewall Whese bacN-end serYers Wo only acceSW requesWs IroP Whe Pound serYer, and ensure WhaW all clienW requesWs PusW be Pade Wo Whe serYer running Pound.

Second, why do the responses differ ( SITE1 firsW, and when you Refresh a Iew WiPes, S,T(2)? Pound disWribuWes incoPing requesWs Wo eiWher oI Whe configured bacN-end serYers, based on Wheir SrioriWy. As noWed earlier, we deliberately entered different content in each index.html file so we'd Nnow which siWe Whe resSonse caPe IroP. HoweYer, in an actual working environment, all Web servers should be serYing Whe saPe conWenW (iI iW's sWaWic conWenW, WhaW is).

RePePber our www.site1.com and www.site2.com virtual hosW siWe naPes? They are obsoleWe or unused; all access being through mound, the only address that matters is that of the Pachine running Whe Pound serYice.