In some cases, additional layers of network devices will alter the http or https traffic generated on the application server sent to the client’s browser. Here are some tips to help troubleshoot behavior:
- Have the direct connection to the application server temporarly unrestricted, and allow logins directly to the application server port. For example, access http://appserver01:8001, http://appserver01:9080, http://appserver01:7001. If the issue cannot be observed at that level, then step one layer back (Web Server) and run the test there. If it works, then step one layer back, and test on the Load Balancer, or Security Filter layer.
- Once the layer that introduces the problem has been identified, engage with the support team for that layer, and explain the situation. A network trace, Fiddler log, or screenshot of the browser with the developer tools console open greatly increases the chances of tracking down a specific configuration change on the load balancer or security filter layer.
Common issues encountered:
- Blocking some files from being downloaded from TRIRIGA, or being sent through notifications. For example .xls or .pdf files with Russian or Cyrillic characters.
- Blocking some requests that seemingly have special characters, or combination of characters. For example, a double slash ( // ) contained within the path or request string.
- Altering the protocol scheme from https to http. Depending on the ssl termination point, browsers may request non-secure content when accessing secure https urls.