More IP addresses bound to the external interface...

I want to publish several HTTPS servers so I bound enough IP addresses to the
external interface and configured the appropriate outgoing web listeners. I
also want to use that machine as a foreward proxy for my internal users. What
I observe when I look at the output from a netstat -an is that the external
interface listens on all IP addresses on both HTTP and HTTPS allthough I have
published one HTTP and one HTTPS site.
This looks a lot like the behavior I know from IIS called socket pooling. Can
this be disabled?
What IP address on the external interface will be used as the source address
for outgoing forward proxy traffic? Only the primary?  All?
 
Thanks,
Han.

Other related posts:

  • » More IP addresses bound to the external interface...