Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Static content served through the FCM IAC Gateway is not cached



We have done analysis on the web server access logs and found that content such as JS, image and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway.
PRPC 7.1.4
Oracle 11g
IE 8 & 10

I have checked that expiry times on content through the FCM gateway appear to be correct (the same as when requested directly).

I have checked several machines and all are set to "every time I start internet explorer" for the Check for new versions setting, I believe this is the standard setting for the bank and that all users will have this setting.

The issue is consistent across all environments including production. I have just recreated in UAT 3 for the purpose of providing the fiddler traces. The tracer I provided was after clearing the browser cache and then repeating the same action several times both directly and via IAC. This therefore shows content being requested only the first time when going direct and repeatedly when going via the gateway.

Steps to Reproduce

Open the same case multiple times directly from PRPC ( and observe the fiddler trace - static content is not requested multiple times.
Repeat the test opening the same case multiple times via the gateway ( and observe that all content is requested every time.

Root Cause

Proposed Solution: 
Changes to PegaCompositeGadgetMgr.js :- removed the appending forward slash from thread name in finalizeNavURL method when the request is issued to gateway . 
Changes to in prGateway:- removed mIsDartmouth from logic where access hash group is added for static resources and no thread name is present in request url.

The customer was in fact not facing the issue from the PRPC layer but from the CPM layer which has it's own javascript triggering the issue (see SR-124897).


This issue is resolved by hotfix item Hfix-20591
Suggest Edit

Published January 31, 2016 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us