Static and Dynamic content URL

I would also like to understand more about these requirements. Why do we need two new domains, would a sub domain suffice? Do we need to site up sites with these domains, and if so, how do we configure them? We are using IIS for our web server.

I need to know about the requirement for this too but the documentation didn't really elaborate much. We have the application server and web server (IIS) installed on the same server with only one site URL. What should we do? Should we create a another different site URL in IIS pointing to the same place?

The documentation is really very poor. We have the same issue and we are blocked. After many tests from our side, The only solution is to have 2 new domains for this feature, but this in a not so small company requires a lot of work to do and lot of people involved. Appian should enable the use of sub-domains for this feature.

I have an open support case with tech support, and they have told me they are working on updating the documentation. However they have not provided a timeline on this. I'm trying to get them to provide some guidance in the meantime, and if they do, I will share via this thread. The requirement for two new domains is considered best practice in the industry, so it will not be going away.

Hi Josh Burwell did you ever get a respond back from Appian regarding being able to use different sub-domains in Sites?

Hi erickp

Below is the reason why Appian doesn't support sub domain for these requirements as documented here:

User-uploaded files and third-party extensions may contain JavaScript code and/or set cookies that pose a potential security risk to your users. Web browsers have built-in security measures that prevent different sources of web content from interacting in dangerous ways. These protections are only applied when content is served from separate domains (not separate subdomains). Appian's URL validation mirrors this browser domain comparison behavior to ensure that your users are safe.