The custom developed header can be returned if you open the backend application directly.
However after you integrate it into HTML5 application, the custom developed header cannot be forwarded from backend application to HTML5 application.
For instance, you develop X-Content-Type-Options header for your backend Java application. And you open this Java application directly in BTP Neo environment. From Developer Tool(F12) of browser, X-Content-Type-Options header can be returned from Java application.
Then you integrate the Java application into your custom developed HTML5 application. At this time, the X-Content-Type-Options header cannot be returned from backend Java application when you call it in HTML5 application.
SAP Business Technology Platform, Neo environment
header, custom developed header, approved header, html5, backend application, headerWhiteList, neo-app.json, X-Content-Type-Options, Java application , KBA , BC-NEO-RT-HTML5 , Runtime HTML5 Applications , Problem
About this pageThis 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.