SoapHttpClientProtocol throws NameResolutionFailure, not ProxyNameResolutionFailure

Question

SoapHttpClientProtocol throws a WebException with status NameResolutionFailure when the proxy name is invalid. How then can I tell if it's the proxy or the destination that is in err?

I'd rather not perform a check if the proxy server exists when a NameResolutionFailure shows up. The only think I can think to do is check the WebException.message property and see if it contains the proxy name vs. the destination name, but this seems icky. Is it the best available?

Why do you care which is missing? What will you do differently in either case? — John Saunders, Nov 29 '10 at 21:05

score 0 · Accepted Answer · answered Nov 30 '10 at 14:55

0

Check the message property, I suppose :/

answered Nov 30 '10 at 14:55

Dlongnecker

3,008
3
25
40

SoapHttpClientProtocol throws NameResolutionFailure, not ProxyNameResolutionFailure

1 Answers1