I'm not sure if the proxy's request is capable of following the
redirect. What I'm guessing is that IE gets a redirect request and
handles it for you. Try connecting directly to the WEbServiceServer
and see if it works.

Why are you trying to redirect the request?

Hi Javier,

If the seetup the proxy correctly it will work. But this is not the senario
I'm iterested in.

Our software should be able to handle this senario. We've got customers that
set up their proxies with mapped URLs.

Many thanks,
Greg.

Hi,

The bottom of this article anticipates your scenario.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/Service08062002.asp

Good Luck.

Hi,

What the article describes breflly is the fact that we can trap the
exception and re-issue a new request to the new location.

This wouldn't work for 2 reasons:

1. Only the proxy server can access machines outside the firewall. So
re-issuing a new request to the machine outside the firewall wouldn't work.

2. The new location returned by HttpResponse.Headers["Location"] as
described in the article still points to the original location. So, there is
no way of getting the new location.

Many thanks,
Greg.

In the absence of url mapping, how would the request go to the correct
host with the right service behind the firewall? ...I'm assuming that
the proxy/gateway would managing and forwarding the request to the host
behind the firewall.

What happens when the consumer of the web service makes a request
directly to the real url of the web service using the proxy?
So in your example:

myWebService ws= new myWebService();
ws.Url = "http://WebServiceServer/VirtualFolder/SomeWebService.asmx";
ws.Proxy = new WebProxy("proxyServer", 8081);
ws.Method1();