We have a production web database with a replica on another production server. The JavaScript and CSS files are indluded on every page. Depending on where the users access the site from or what bookmark they use, they may be accessing both servers during 1 session.
The problem we’re seeing is that periodically one of the servers cannot find the indcluded *.js file. The file included is relative to the server and the design on both of the replicas is identical, so we’re puzzled as to why the server can’t find the included file. Everything else on the page loads as expected. The code will be included and work fine one day and then won’t get included another day. =(
HTML for including the file:
Note: On one of the servers we do have the “web rule http response header” set to NOT cache so the user’s credentials for logging in and out with R6 wil function properly.
We’ve found that refreshing the design of the database that isn’t including the *.js corrects the problem. However, that isn’t a practical solution for a working application. The included *.js file contains numerous functions that control the site, so the site breaks down considerably without them.
Any ideas on why this would happen or how to fix it?
Angie Schottmuller