Getting 400 bad request with WCF service called through WebRequest using C?

I'm saw antoher post you did and I think that you and I are currently working on the same thing. Invoking web services dynamically. Loading WSDLs, using dynamic proxies and reflection and all that fun stuff.

I'm saw antoher post you did and I think that you and I are currently working on the same thing. Invoking web services dynamically. Loading WSDLs, using dynamic proxies and reflection and all that fun stuff.

I have a suggestion for this error that you see. I have had a similar issue with one of the web services I used. Even if the Action in the header is supposted to be optional, it did manage to get my call to fail when I passed in the address (uri) as you have.

When I passed in the name of the operation instead it worked. So try and change this: req.Headers. Add("SOAPAction", "tempuri.org/GetSimpleType"); To the name of the method in the WSDL instead.

That is the name of the System.ServiceModel.Description. OperationDescription. It is probably "GetSimpleType".Req.Headers.

Add("SOAPAction", "GetSimpleType").

Karin Glad to see someone working on similar thing otherwise I didn't find any resource for WCF/Soap Request. Changing the code as you suggested didn't make it work either :( May be I am still missing something here. At first I thought that it may be 'coz of the way wsdl is being generated for WCF (multiple xsd reference) but then I generated single wsdl and it failed again.

Can you share the piece of your code? – kuul13 Apr 6 at 13:04.

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.