Service Client Receives "Bad Request (Invalid Header Name)" Respon

[EagleRedHighF...@discussions.microsoft.com]

I have written a Web Service that works with my test harness written using
VS2005. However, a client to the service consistently receives a "Bad
Request (Invalid Header Name)" response for each request. He is using
another development environment that requires that he create the actual
request via multiple calls to a library to construct the request. I have
sniffed the traffic from my harness program and the requests look like the
following:

POST /TotalService/POSService.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 2.0.50727.1433)
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://www.coltpos.com/TotalService/ExecuteBasic"
Host: www.coltpos.com
Content-Length: 1126
Expect: 100-continue
Connection: Keep-Alive

HTTP/1.1 100 Continue
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
.
.
.
</soap:Envelope>

The client requests look like:

POST /TotalService/POSService.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; .NET CLR 2.0.50727)
Host: www.coltpos.com
Content-Length: 1221
SOAPAction: "http://www.coltpos.com/TotalService/ExecuteBasic"
Expect: 100-continue
Connection: Keep-Alive
HTTP/1.1 100 Continue

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
.
.
.
</soap:Envelope>

His responses are:

HTTP/1.1 400 Bad Request
Content-Type: text/html
Date: Mon, 18 Aug 2008 11:21:45 GMT
Connection: close
Content-Length: 42

<h1>Bad Request (Invalid Header Name)</h1>

Does anyone have any idea of what is going wrong with his requests?

As always any input is greatly appreciated.

Thank you,
Eagle

[Arnold@arnold.com Mr. Arnold]

"Eagl...@HighFlyingBirds.com"
<EagleRedHighF...@discussions.microsoft.com> wrote in message
news:EFFA12D6-C314-4209...@microsoft.com...

<snipped>

>
> His responses are:
>
> HTTP/1.1 400 Bad Request
> Content-Type: text/html
> Date: Mon, 18 Aug 2008 11:21:45 GMT
> Connection: close
> Content-Length: 42
>
> <h1>Bad Request (Invalid Header Name)</h1>
>

http://support.microsoft.com/kb/828726

Maybe, you need to start looking at the raw HTML/data that's being sent.