For some time we have not been able to use the "Use runtime optimized JavaScript and CSS resources" feature because the aggregated JS and CSS links are always broken. When I inspect with the F12 IE developer tool, the CSS files just do not load. When I look at script, the aggregated JS file returns "Could not find file".
This issue only occurs when there are two or more JS or CSS resources that get aggregated. If it is only one resource (no aggregation), the link works.
I do notice that aggregated "internal" JS files are successfully found and loaded. It is just the ones within the app that are not found. This problem is consistent amongst all apps, which leads me to think this might be a server issue, perhaps a setting that was missed.
Other info: This problem existed in 8.5.3 and it still exists in Domino 9.0.1FP3. All users use IE 7 or higher. By "internal" JS files, I am referring to those files Domino loads when, for example, I request dojo modules. The path for these is "https://serverpath/xsp/.ibmxspres/.mini/dojo/..."
My db-specific resources, when aggregated, are "/dbpath/xsp/.ibmxspres/.js/..." and "/dbpath/xsp/.ibmxspres/.css/...".
If anyone has some suggestions on what the cause might be, I would appreciate hearing from you.
The problem appears to be the DSAPI filter used with Siteminder. When the filter (DominoWebAgent.dll) file is removed, the problem goes away. As we are going away from Siteminder soon, we will just wait to use the aggregation tool. Thank you to each person who offered their thoughts on this issue.