When you are having trouble with rendering Mod graphs in the web player, check the HAR file. If all content requests (such as main.css, bundle.js) are returning a 302 status code and if there is a load balancer configured for Spotfire Servers, the load balancer configuration in front of Spotfire needs to be corrected. The issue is happening because the load balancer redirects the request for the "main.css" file to a location named "/my.policy", instead of serving the necessary resource. This redirection disrupts the rendering of Mods in the web player.

All

Static Mod resources are typically accessed without requiring authentication cookies or tokens, as they are rendered within a sandboxed iframe where authentication credentials are not present. This design ensures that Mod resources are publicly accessible.  Here are the steps to be done to resolve the issue:

1. Setting up an authenticating reverse proxy: To address this issue, consider implementing an authenticating reverse proxy in front of the Spotfire Server. Detailed instructions for setting up an authenticating proxy can be found in the documentation below:
Setting up an authenticating reverse proxy in front of the Spotfire Server

2. Allow fully unauthenticated requests: Ensure that fully unauthenticated requests (without cookies or sessions) are permitted to access the /spotfire/wp/mods/ path within the reverse proxy layer. This adjustment will enable the necessary resources to be fetched without encountering redirection issues.
 

This article offers guidance for resolving the Mod graph rendering issue in Spotfire Web Player with Load Balancer Setup, addressing challenges posed by redirection in load-balanced configurations.

Doc: External authentication

https://docs.tibco.com/pub/spotfire_server/latest/doc/html/TIB_sfire_server_tsas_admin_help/server/topics/external_authentication.htm

Creating a HAR file in Chrome:

https://support.hmhco.com/s/article/Creating-a-HAR-file-in-Google-Chrome