You would prefer to add it for each file type that can also be done) this should use the type “application/octet-stream”.Īllow special characters to be escaped in file paths.
Through a lot of trial and error, working with our customers, we have been able to find the following fixes:Īdd the MIME Type for the “.wasm” extension to be “application/wasm”.Īdd the MIME Type for the other low-level files we provide (we normally recommend just adding the default extension which is typically just “.” but if IIS tends to give us the most trouble with CheerpX, due to its strict security policies. Make sure that you have given them the correct domains to whitelist, these should be the origins of the flash content, and not the pages they are hosted on. If you get in touch with Harman, they should provide you with a new libHCSFP.so with an updated 1 month license. SWF files from a domain that is not whitelisted. You have correctly configured CheerpX, congratulations! Your issue is that the Harman library is either expired, or is being given. If you see a logo that looks like this in place of your application: If you see a 404 error getting pp.js, your server has not been configured correctly, because the application cannot pull pp.js, which is a standard Javascript file. These are absolutely expected, and can be made to resolve to 200’s via correct server configuration, so that an end user will see no problem. The CheerpX virtualization engine will sometimes make calls to a virtual linux environment that doesn’t exist, and some will return 404 errors. CheerpX is working as intended, don’t panic.
0 kommentar(er)
