SAP Knowledge Base Article - Preview

2397469 - SAP Mobile Platform 3.0 sets unallowed a Cache-Control Header

Symptom

Performance issues with the Fiori Client.

There are no caching headers set.
 
The Fiori Client did not store any data.
Did a trace for the requests of the Fiori Client.

The trace shows, that the SAP Mobile Platform 3.0 writes to every request the following header:

Cache-Control = no-store, no-cache, max-age=0

In this environment there is Apache 2.4 as Reverse Proxy, who then goes on SMP and then to the SAP Gateway, which has the Launchpad installed.

The header above is only not set, if you go direct to the SAP Gateway.
So this confirms, that the header is set by the SMP.

What can you do, that this header is not set  anymore ?

 


Read more...

Environment

  • SMP 3.0 Server SP10 PL06
  • Android devices use the Custom Fiori Client,
  • but for iOS uses the native app from the Apple App Store

Product

SAP Mobile Platform 3.0

Keywords

Cache control header, ControlCacheFilter.java,Cache-Control, no-store, no-cache, max-age=0 , KBA , MOB-ONP , SAP Mobile Platform on Premise , Problem

About this page

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

Search for additional results

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