Hi Pega support, we have a use case that we hope you have advice on how to support in Pega Cloud:

External websites will submit cases to our Pega instance on a REST API, but first they need to get some content from our Pega instance. Half of it is dynamic metadata which we have covered with a REST webservice we expose, which they call. The other half is static content - e.g. .css and .js files which we need to host for them, we are looking to find out how. We would like to host that static content on the Pega servers to be retrieved from the external websites. We need static content visible as file URLs and returned with correct MIME types without a web session needed in the URL. Do you know of a supported configuration in Pega Cloud or whether there is a policy around that?

Ideally we would upload content directly to a folder on the servers and bypass the Pega DB, is that supported, or is there a policy around that?

Specifically:

1) As per your documentation there is product support for extracting content to edge servers. Does Pega Cloud have edge servers we can request the content to be deployed to? Deploying static content to an edge server (pega.com)

2)It seems generally static files are only delivered in the context of a web session in Pega.   Although we can configure custom servlet configurations in Pega Cloud, it seems we cannot upload/customize servlet configuration code e.g. a file serving servlet. It also seems all the existing servlets will first establish a session and then serve content under the URL for that session.  Are you able to confirm whether that is true or there are exceptions?

3) Do you know of customers who have used REST services using filenames at the end of the URLs and returning the unencoded content and MIME types of the files, or guidelines for doing so?

Thank you and regards