>Good info...
>
>In response to his question though I doubt this is what the problem is. WinINet will work ok on most servers if there's no load or light load. Corruption occurs only under load...

Also-
corruption under load is a different issue altogether, due to the way WinInet handles concurrent calls from a multithreaded client (IIS). The Proxy config issue is only an issue when using WinInet from a client with no identity (such as a service). If you're using it with WWWC, you're most likely using it under the account of the logged on user, or whatever account your COM instances are configured to run under, so you wouldn't see this problem.