POST /axis2/services/resources HTTP/1.1 Host: bsfso1:9080
this is the http header of the ajax client I am using, it worked fine with axis1 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-gb,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: close X-Requested-With: XMLHttpRequest X-Prototype-Version: 1.3.1 Content-Type: application/xml SOAPAction: "" Referer: http://localhost:9080/axis2/ajaxclient.html Content-Length: 154 Cookie: JSESSIONID=529D0FE433A10635D62CAEB7082256C5 Pragma: no-cache Cache-Control: no-cache Leaving it like this makes axis2 1.2 to reply in this way <faultstring>The endpoint reference (EPR) for the Operation not found is /axis2/services/resources and the WSA Action = null</faultstring> if I change the Content-Type form application/xml to text/xml all works fine.. Is it a regular behaviour? would it be possible to accept as soapcalls also calls with Content-Type: application/xml and empty SOAPAction: ""? or such a client header has to be deprecated and not used at all? thanks -- View this message in context: http://www.nabble.com/axis2-bad-header-for-soap-calls-tf4383353.html#a12495734 Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
