SAP Knowledge Base Article - Preview

1711486 - ESI - Error when calling Web Services from a browser or transaction SICF


When calling an SAP Web Service (endpoint) URL from a browser, one of the following errors occurs:

  • SRT: Wrong Content-Type and empty HTTP-Body received: ("HTTP Code 200 :  OK"),
  • 415 Unsupported Media Type,
  • Processing error: more details in WS Error Log (transaction SRT_UTIL) by selection with UTC time stamp 201xxxxxxxxxxx.
  • This page isn't working right now
  • Error : This page is not working. 
  • HTTP ERROR 415 
  • HTTP ERROR 500



  • ABAP Web Services
  • SAP NetWeaver
  • SAP NetWeaver Application Server for SAP S/4HANA
  • ABAP PLATFORM - Application Server ABAP


ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions


Webservice, Web Service, Webservices, Web Services, ESI, ESI_GDPR, ESI_STD, SOAP service in a browser, HTTP Post, HTTP 'POST', valid SOAP test, valid SOAP request, Web Service Navigator, SPROX_HTTP_REQUEST, HTTP ERROR 500, This page isn't working right now, Wrong Content-Type and empty HTTP-Body received, HTTP Code 200, 415, Unsupported Media Type, This page is not working, HTTP ERROR 415, SICF, Test service , KBA , test service from sicf , web service test with get method , web service navigator , BC-ESI-WS-ABA , Web Service and SOAP - ABAP , BC-SEC-WSS , Web Services Security for ABAP , BC-DWB-WS-ABA , Web Service Tools - ABAP , BC-ESI-WS-ABA-RT , WebServices ABAP Runtime , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.