DotNet Web Service

[Rastafas]

I am having trouble contacting an installed .net webservice from .net code. The service works from the browser, and all the methods seem to work when invoked with HTTP GET requests.

When invoked as a Soap service from .NET code, this is what is posted to the webserver:

POST http://localhost/kwws/service.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: "localhost/GetSurveys"
Host: localhost
Content-Length: 247
Expect: 100-continue
Proxy-Connection: Keep-Alive

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body>
<GetSurveys xmlns="localhost" xmlns:a="http://schemas.datacontract.org/2004/07/CallSoap.WebChoices" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"/>
</s:Body></s:Envelope>

The server sends back this 415 error:

HTTP/1.1 415 Unsupported Media Type
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Length: 0
Connection: Close
Date: Sun, 16 Mar 2008 14:17:43 GMT
Server: Abyss/2.5.0.0-X1-Win32 AbyssLib/2.5.0.0

I'm apparently too stupid to figure out how to fix this, so I hope somebody can give me a kick to see what I'm missing.

[aprelium]

Rastafas,

Error 415 is generated by ASP.NET or the ASP.NET application directly.
_________________
Support Team
Aprelium - http://www.aprelium.com

[Rastafas]

I understand that the webservice code itself is generating that 415 error.

What I don't understand is this:

1) Installing the same exact code under IIS, this doesn't happen, with the same exact code. The webservice is discovered by the calling application just fine. The webservice is consumed by the calling application just fine.
I don't want IIS running on this particular box, that's why I hoped Abyss, would be able to serve this up.

2) Running under abyss, the webservice is discovered by the calling application just fine. It generates the above error when the calling application trys to consume its methods. The calling app generates the same exact request that I copied in the first mesage whether it is trying to talk to IIS or ABYSS. The only difference is IIS works, and under abyss I get the 415 error.

If the webservice code is causing this error, where do I look? The code that handles the method calls doesn't do anything fancy. It is pretty far removed from any of the protocol stuff. I'd like to think I could get this working without debuging the .net ancestor class the webserivice is inherited from, especially since the same exact code works under IIS. And again, the service works just fine called from the browser. I could code the calling app to call it the way the browser does, but that sort of negates the reason for using SOAP, since it wouldn't be (SOAP) anymore.

If the answer is, that once again Microsoft smells its own and I'm screwed, I'll accept it, but I was hoping for something different.

Thanks!

[aflynt]

My hypothesis is that the ASP.NET hosting process ignores the first header after the request. I've confirmed this behavior while troubleshooting my own issues with Request.UserAgent. Try sending a request with a dummy header after the post line and see if that works:

[aprelium]

The problem has been fixed. Please contact us to get un updated ASP.NET connector.
_________________
Support Team
Aprelium - http://www.aprelium.com

[slavetonone]

I think I am having the same issue, can I please get this update also? Thanks!