Request handled okay when issued by browser, but not when issued by ASP.NET application on the same machine?

I think you should try without the params in the url.

I think you should try without the params in the url. WebRequest request = WebRequest. Create("localhost:90/Controller/Action"); request.

Timeout = 10000; request.GetResponse(); if it does work you need to add some user-agent headers to allow the use of params. Also you should probably look at WebClient. MSDN personally I would also look at using IISExpress or IIS to develop this kind of solution.

Just an outsider's observation here, consider making this call to the second webmethod via an ajax call from the browser and aggregate the results clientside using javascript (jQuery).

I would try and use the overload of WebRequest. Create that takes a URI object, that way you can rule out a fat-fingered URL.

Two hours debugging - and it turned out that service at port 90 would redirect the request back to the service at port 100 but wouldn't provide a required parameter in the URL, so the handler in the service at port 100 would throw an exception and return the HTTP 400 which was then reported by the GetResponse(). The solution was to change the logic so that there's no redirect for this specific request because the redirect would make no sense for this specific request. And the jury finds both Cassini and ASP.NET to be not guilty.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.