|
| We are having problem in accessing a webservice deployed on Websphere 6 application server thru IBM Http server.
When the client is using SOAP 1.1(Axis 1.0) , we are getting a 404 Not Found error from the web server.
At this time, the request header is as below from tcpmon)
==================================
POST /TestWS/services/TestWS HTTP/1.0
Content-Length: 423
Host: 192.168.130.89:9999
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
==================================
When we tried with SOAP1.2(Axis1.2.1), we are able to invoke the web service.
At this time, the request header is as below:
==================================
POST /TestWS/services/TestWS HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.2.1
Host: 192.168.130.89:9999
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 349
====================================
Has anyone come across this? Is there any way to tell the web server to allow the Axis 1.0 request
header to be processed on Webspehere 6(instead of blocking the rquest)? Since ours is massive application written in Axis 1.0, it will be
a huge task to get the client code going with Axis 1.2.1, we think.
Please share your thoughts/suggestions.
Thanks
|
|