I see a very strange problem on our live platform, which consists of four Windows Server 2003 web server windows located in a cluster behind an ISA cluster server. They all work with IIS 6. We have a need for webservice requests that must be made from the .NET 2.0 webapp to the outside world, so that we use the "defaultProxy" configuration section to specify the proxy server for outgoing requests, as shown below:
<system.net>
<defaultProxy>
<proxy proxyaddress="http://cache.mydomain.co.uk:8080"
bypassonlocal="true" />
<bypasslist>
<add address="monkey.mydomain.com" />
<add address="www.mydomain.com" />
<add address="192.168.0.1" />
</bypasslist>
</defaultProxy>
</system.net>
As you can see, we also specified a bypass list, so webservice calls in our web application that makes a call on another website on the same server do not miss the proxy.
This works for the most part on our live system during the day, but as the system is under heavy load, web service requests to be bypassed by the proxy suddenly begin to be routed through the proxy server and will remain that way until the pool utilization is completed applications. At this point, he returns to how it should work. This happens on all four servers; usually within minutes of each other.
I deduced the proxy settings that are used during the web service call, and I can see the bypass list when everything works correctly and the "bypassed" property is "true" for the local webservice URL. However, when it goes wrong, I can no longer see the workaround and bypass the false property. The proxyaddress property remains unchanged all the time.
, ,
-
WebProxyWrapper, , ,
WebProxy.
- - ,
?
user173602