cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Browser Cache Issue

Former Member
0 Likes
2,362

Hi Everybody,

We are using SAP Netweaver 7.3 Portal and integrated ABAP webdynpro applications by creating iviews in portal. SSO is configured and working fine.

Issue:-

Browser cache memory is not clearing  when we log off the respective user from the portal –  due to this applications behaves as same user even we log in with different user. If we manually clear the Browser cache, we are able to see the second user's application.

Any suggestions on how to resolve this issue will be really helpful.

Thanks,

Krishnaveni.

View Entire Topic
SandipAgarwalla
Active Contributor
0 Likes

Krishan

What is the cache property set for the ABAP web dynpro application in the Portal PCD? What is the value?

Normally you can cache iviews in the client side (browser), but it normally should not show same content for diff users specially if the Content is dynamic...

If its static content (like HTML), then its retrieved from the browser cache..

Thanks

Sandip

Former Member
0 Likes

Hi Sandip,

Thanks for your valuable input.

Below are the Cache related Property and its value in the Portal PCD which is set for ABAP WD application.

Cache Level = None

Cache Validity Period = -1

Thanks,

Krishnaveni.

Former Member
0 Likes

Hi Krishnaveni,

Have you tried to access the ABAP Webdynpro app directly (e.g. not via the portal)? Is it the portal that is caching (e.g. the Portal Menu) or is it the Web Dynpro App that is being cached?

Thanks,
Simon

Former Member
0 Likes

Hi Simon,

Thanks for your reply.

Masthead is changing correctly for different logged in users and the roles are appearing correctly. When we click on the wd application iview it is taking to the previous user's content. If i clear the browser cache, it will give the correct content.

Thanks,

Krishnaveni.

SandipAgarwalla
Active Contributor
0 Likes

Have you enabled any of these on the Server

1) PCD Cache

2) Portal runtime cache

3) Navigation CACHE (though this should not affect)

Try clearing the PCD Cache from the server once, it may help (not sure, but wild guess)

Else raise a Ticket with SAP..

Thanks

Sandip