Background:

We are evaluating the feasibility of caching static content (CSS, JS, images, fonts) via AWS CloudFront for our Pega application using Theme-Cosmos.

Observation:

We observed that static content URLs follow this pattern:

https://<domain>/prweb/PRServlet/app/<AppName>/<unique-string>/<images|webwb>/*.<png|svg|etc>

The <unique-string> appears to be a hash-like identifier. We suspect this may be a session or requestor ID.

Questions:

1. What exactly does the unique string (<unique-string>) in the URL path represent?
2. What are all the URL paths from which static content is served?
3. If the identifier is session-specific, does this mean that CloudFront path-based caching would be ineffective for static content, since the same resource would have different URLs for different sessions?
4. What are the best practices for caching static content in a Theme-Cosmos application?

Environment:

• Pega Infinity 24.2
• Theme-Cosmos (Traditional UI)
• AWS deployment with CloudFront

Note:

• We are aware of the "Extract Edge Server Files" feature for static content deployment, which we are evaluating separately. This question assumes a scenario where that feature is NOT used.
• Since we are using Theme-Cosmos (Traditional UI), the "Constellation Pega Static CDN" is not applicable to our environment.

Thank you for your assistance.