0

I have an old .NET 2.0 app connecting to the asmx web service. I need to debug the web service, but when I run it locally, I always receive 400 - Bad Request response. Trace for the web service gave me a little more details - the exception which was thrown is Root element is missing. Then I tried to catch the traffic with Fiddler - but apparently it can't catch it even when app has forced proxy to localhost:8888. So I used the idea from here to log the soap message. But result was supprising - soap messages logged for this very service was blank. For other web services this method works.

Any ideas what may cause this behavior, or how can I trace it? The only idea I have now is to confirm that the soap message is blank with WireShark...

William Kinaan
  • 28,059
  • 20
  • 85
  • 118
Chris W.
  • 366
  • 4
  • 15
  • add a period after localhost. so it looks like this localhost.:8888 you can also add an entry into the host file. – Chuck Conway Apr 03 '13 at 12:07
  • No luck, didn't caught the soap message after that change. Version of Fidller I use now is 2.4.2.6 (the most recent currently). – Chris W. Apr 03 '13 at 13:16

2 Answers2

0

You get the 400 - Bad Request error because the request cannot be parsed. It cant be parsed because it is an empty message, hence the Root element is missing error occurs when the XML parser wants to read your message. Verify that the message you send to the service is not empty.

w5l
  • 5,341
  • 1
  • 25
  • 43
0

Today I got a minute to take a look at the problem again and I found something interesting. In web.config file for the web service there was declared paths for directories used by the web service and one of the paths did not exist. It was not used by the methods which returned 400 bad request response, but after fixing the directory path to the one that exists the bad request problem has disappeared. Thanks for your help on this!

Chris W.
  • 366
  • 4
  • 15