Oh, to answer one more question asked, nsvhr/nsunix certainly doesn't choke at high throughputs. I did some benchmarking of it against Apache and at high hit rates, it just stomps the competition by at least a factor of two to three in speed. Under appropriate conditions nsvhr/nsunix can realistically save you the money you might need for either additional IP addresses, additional systems/processors, or both. nsunix works it's magic by eliminating at least one copy of the content through the proxy, so efficiency goes up the more your content tends to be larger rather than smaller amounts.
That's why the fact I can't figure how to solve the IE POST bug is so annoying.