on 04-01-2014 9:47 AM
We have created a Remote function module and developed the Web service for this RFC. We have given WSDL file and path to third party (sharepoint application) to consume.
Sharepoint team were successfully calling this web service and received the data from their server side. But when they call this web service from client side (web browser), they are getting below error message
HTTP/1.1 415 Unsupported Media Type
content-type: text/html
content-length: 0
server: SAP NetWeaver Application Server / ABAP 731
Is anybody across this issue and provide your expertise in this issue?
Do we need add any parameter in web service or SOAMANAGER to allow other formats such as html instead of xml?
Appreciate any feedback .
Thanks in advance.
Regards,
Suresh
hi,
i have the same problem that when i connect to a specific webservice i have this message
HTTP/1.1 415 Unsupported Media Type
server: SAP NetWeaver Application Server 7.20 / AS Java 7.30
pragma: no-cache
content-type: text/html;charset=ISO-8859-1
content-length: 1972
date: Mon, 21 Sep 2015 11:36:12 GMT
i cannot resolve this problem
this is my request:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<StartRequest_sync xmlns="http://sap.com/xi/ME">
<StartRequest>
<SiteRef>
<Site>4680</Site>
</SiteRef>
<SfcRequest>
<SiteRef>
<Site>4680</Site>
</SiteRef>
<SfcRef>
<Sfc>615190001879</Sfc>
</SfcRef>
<ResourceRef>
<Resource>04_REPRISE_EMBALL_PKT</Resource>
</ResourceRef>
<OperationRef>
<Operation>REPRISE_EMBALL_PKT</Operation>
<Revision>01</Revision>
</OperationRef>
<UserRef>
<UserId>TESTEUR</UserId>
</UserRef>
</SfcRequest>
</StartRequest>
</StartRequest_sync>
</s:Body>
</s:Envelope>
how can i solve this problem please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh,
This looks like an issue with the web app that executes the Webservice. In the request header they must be specifying "text/html" and the server is mos likely expecting "text/xml". If they change this in the request, this should hopefully fix up the issue.
Cheers,
Katan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh,
That seems a bit odd that they cannot change it. Especially if it is invoked via client side scripting, as you said that they can see the trace in the browser.
Read the following which explains HTTP binding of a SOAP request.
http://www.w3schools.com/webservices/ws_soap_httpbinding.asp
As I said before as they are not providing the correct content type, the server rejects the request. I also said in my original post that the content type should probably be set to "text/xml" but it should be "application/soap+xml", so apologies for that.
The server cannot accept anything other than this content type as SOAP is always in this format. From a security point of view, it does not make sense to try and change it, even if it were possible.
Cheers,
Katan
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.