05-18-2020, 01:32 AM
Hi Celton, and thanks for your quick reply.
I'm unfamiliar with the Javascript console, but I think you may mean a panel I get Firefox 75 to show me when I click Tools->Web Developer->Web Console.
In that log console for my TACTIC page, I see several errors like:
"Loading failed for the <script> with source “http://x.x.x/context/spt_js/applet.js?ver=4.7.0.b02”."
...
"Loading failed for the <script> with source “http://x.x.x/context/spt_js/chart/utils.js?ver=4.7.0.b02”."
ReferenceError: spt is not defined
ReferenceError: spt is not defined
But I see no 403 errors here (unless perhaps I just don't know what a 403 error is, but I filtered the output for "403" and found nothing resulting).
In Firefox, I also did Tools->Web Developer->Browser Console.
In that log console for my TACTIC page, I see several errors like:
"PushDB: update: Ignoring invalid update 0f73a593-7ac2-6646-930f-0315526b9f0c null PushDB.jsm:418
PushService: receivedPushMessage: Error notifying app AbortError PushService.jsm:829
...
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
OpenGL compositor Initialized Succesfully. Version: 2.1 INTEL-10.32.48 Vendor: Intel Inc. Renderer: Intel Iris Pro OpenGL Engine FBO Texture Target: TEXTURE_2D 2
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] 2 network-response-listener.js:84
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified"
There are many others too (19 errors, 42 warnings, some log entries, et. al.) I also filtered this console for "403" and found nothing resulting.
Does this help you figure out what I'm doing wrong? Thanks again for your suggestions. Although I still have the same problem, your suggestions are certainly teaching me a lot about browser features I was previously unaware of, and I very much appreciate that. And I'm optimistic that with a bit more troubleshooting and help from this forum, I'll soon be able to solve the problem.
I did set the devtools.chrome.enabled preference to true in about:config (it was previously false). I'm not sure if that helped or what.
I'm unfamiliar with the Javascript console, but I think you may mean a panel I get Firefox 75 to show me when I click Tools->Web Developer->Web Console.
In that log console for my TACTIC page, I see several errors like:
"Loading failed for the <script> with source “http://x.x.x/context/spt_js/applet.js?ver=4.7.0.b02”."
...
"Loading failed for the <script> with source “http://x.x.x/context/spt_js/chart/utils.js?ver=4.7.0.b02”."
ReferenceError: spt is not defined
ReferenceError: spt is not defined
But I see no 403 errors here (unless perhaps I just don't know what a 403 error is, but I filtered the output for "403" and found nothing resulting).
In Firefox, I also did Tools->Web Developer->Browser Console.
In that log console for my TACTIC page, I see several errors like:
"PushDB: update: Ignoring invalid update 0f73a593-7ac2-6646-930f-0315526b9f0c null PushDB.jsm:418
PushService: receivedPushMessage: Error notifying app AbortError PushService.jsm:829
...
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
OpenGL compositor Initialized Succesfully. Version: 2.1 INTEL-10.32.48 Vendor: Intel Inc. Renderer: Intel Iris Pro OpenGL Engine FBO Texture Target: TEXTURE_2D 2
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] 2 network-response-listener.js:84
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified"
There are many others too (19 errors, 42 warnings, some log entries, et. al.) I also filtered this console for "403" and found nothing resulting.
Does this help you figure out what I'm doing wrong? Thanks again for your suggestions. Although I still have the same problem, your suggestions are certainly teaching me a lot about browser features I was previously unaware of, and I very much appreciate that. And I'm optimistic that with a bit more troubleshooting and help from this forum, I'll soon be able to solve the problem.
I did set the devtools.chrome.enabled preference to true in about:config (it was previously false). I'm not sure if that helped or what.