Customised Module for GVH cannot be loaded with 4.14.4
I'm getting this error:
Refused to execute script from 'XXXXXX.js' because its MIME type ('application/unknown') is not executable, and strict MIME type checking is enabled.
Used to work well in version 4.14.3
-
Same problem. I'd like to piggy-back on this as well.
0 -
Found a possible workaround. In the Desktop/Tablet/Handheld.json.js file find where it calls for your custom module. Mine was like this:
{
"id": "TBWEFMobile_Modules",
"bundleUri": "{ViewerConfigUri}../../Compiled/TBWEFMobile_Modules.js",
"loadModulesBundle": false,
"async": true,
"locales": [
{
"locale": "en-US",
"uri": "{ViewerConfigUri}../../Locales/TBWEFMobile_Modules.en-US.json.js"
}
]
}
Since I noticed that the other JS in the file had no problem I copied my custom module.js file to the "Resources/Locales directory; same as the others that work in the file. Revised code looked like this:
{
"id": "TBWEFMobile_Modules",
"bundleUri": "Resources/Locales/TBWEFMobile_Modules.js",
"loadModulesBundle": false,
"async": true,
"locales": [
{
"locale": "en-US",
"uri": "Resources/Locales/TBWEFMobile_Modules.en-US.json.js"
}
]
}
All seems to work fine now.
1 -
Same issues here, please add me as a stakeholder.
0 -
Same problem for us.
0 -
Same problem here, which results in workflows (Workflow 4) not being able to run anymore after an inactivity of 15 minutes in the viewer. Could it have something to do with '46478: Essentials now sets the X-Content-Type-Options header on all responses.'? (see 'What's new in 14.4.4: https://docs.geocortex.com/essentials/latest/admin-help/Default.htm#ge/admin/release-notes.htm)
1 -
We are experiencing the same problem as Marina. After appoximately15mins our viewers fail to load any data at all. We are seriously considering rolling back to the previous version and losing the last 2 months worth of work. Users are reporting to us that this version is significantly less reliable than the previous and they are spending significantly more time creating maps than they were before. They are telling me that what took 5mins now takes 30mins and I have also experienced this first hand. On top of this we have having issues with layers not displaying on the map even though they should be visible, problems with filters and selections, just to name a few.
0 -
Also, looks like the charts function is not working.
0 -
Hi Everyone,
I believe Marina's assessment is correct. The addition of the X-Content-Type-Options header causes the viewer to observe very strict rules about what content it may interpret, which unfortunately is breaking several things in the viewer, including periodic token refreshes and loading of custom module javascript stored in the Essentials Site folder.
I'll publish an article next week outlining what can be done to avoid it, but the gist is that we need to back out the headers that set this behavior temporarily (to revert to 4.14.3 behavior) until we can fix it properly.
Regards,
-Malcolm Walker
Technical Support Manager - VertiGIS North America0 -
Thanks for the information, Malcolm!
0 -
Here's a temporary solution that works for me:
1. go to the 'REST' folder of the viewer, and find the Web.config file . (eg. C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\Web.config)
2. search for 'nosniff'.
3. comment the custom header. So it looks like this:
<httpProtocol>
<customHeaders>
<remove name="X-Content-Type-Options" />
<!-- <add name="X-Content-Type-Options" value="nosniff" /> -->
</customHeaders>
</httpProtocol>2 -
Thanks, the temporary solution works for custom modules to be allowed, but the chart function still does not appear with this workaround.
0 -
Thank you @... for the fix!
Malcolm Walker - I tried searching for a write-up on this issue to no avail. Are there any further resources on how to properly resolve this issue?
0
Please sign in to leave a comment.
Comments
12 comments