issue: odata entity loaded from browser cache (msie)

[Former Member]

Hy @all,

iv'got a problem with Internet Explorer and Netweaver Gateway 7.02 odata service.

i used the model.create function to add new data, when i read the data (entitySet) the response data came from cache with http response code 304 (not modified). this seems to be an issue.

i found a solution @

bit this is no solution for me, this is a hack. i dont want to use this hack.

my questions are:

- does this problem still exists in current netweaver releases?

- can i customize the netweaver to use non-caching headers eg. in "spro" ?

- anybody other solutions?

thanks, Danilo

[Former Member · Accepted solution]

Hy again,

the manipulation of the service gateway response header is advised as documented in the sapui5 docs and at SAP Help Portal

Thanks for your tip.

I need to rectify my opinion - this seems to be the only solution for now. I don't know why this isn't configurable in service builder "SEGW".

• i used to redefine the following methods:

• insert the following code before
  "try. CALL METHOD SUPER->/IWBEP/IF_MGW_APPL_SRV_RUNTIME~...."

method /IWBEP/IF_MGW_APPL_SRV_RUNTIME~......

  " --- no cache ---
     data: LS_HEADER type IHTTPNVP.
     LS_HEADER-NAME = 'Cache-Control'.
     LS_HEADER-VALUE = 'no-cache, no-store'. SET_HEADER( LS_HEADER ).
     LS_HEADER-NAME = 'Pragma'.
     LS_HEADER-VALUE = 'no-cache'. SET_HEADER( LS_HEADER ).
  " --- END no cache ---

     try.
         call method SUPER->/IWBEP/IF_MGW_APPL_SRV_RUNTIME~....

• save, activate, test ..

[Former Member]

This will always clear your cache

[Former Member]

hi ,

yea, i know this hack.. but this solution seems a little unclean to me. there must be a comprehensible way to do this. i really don't want to redefine these interfaces. caching is generally a good way to minimize transfers therefore i resist permanent headers (especially when I am compelled due to internet explorer problems).

[Former Member]

Oh I didn't see you already found that solution. Sorry

[Former Member]

ok, my simple workaround for this...

while we are using jQuery requests in SAPUI5 the solution is following javascript

  // disable caching on GET-Requests.
  if(sap.ui.Device.browser.internet_explorer || sap.ui.Device.browser.msie) jQuery.ajaxSetup({ cache: false });

this prevents ajax calls (eg. data GET requests) to be cached by the Internet Explorer.