Hi,
I have a similar problem to this but with a different environment.
Accessing SOAP services v2.2 running on Linux on WepSphere AppServer, these
services being accessed by IBM HTTP Server (Apache) running on a Windows
2000 server machine.
The http connection seems to be very temperamental - m
This problem usually is caused by the slight differences in different
implementation of HTTP protocol. e.g. If you are using a Windows client
while your service are running in Tomcat/HP, you are likely to get this
error. Normally this error can be safely ignored.
HTH.
-Chengmin
-Original Me