I think that the problem you see is because you're reading the files using the file:// protocol.
Can you try enabling the HTTP server integrated in Enterprise Browser and see if this solve your issue?
you need to enable the option in the Config.xml file:
Regarding the "Signal" tag in the Config.xml, you should try to set it as visible:
Thank you Pietro, the signal is now visible. But I still have the problem with the locally stored data. I'm actually not sure how to set the path correctly and if the port is relevant. The files are stored in a folder in the root directory ( \XX\YY\). The error in the logfile shows:
Not allowed to load local resource: file:///XX/YY/pic.gif
I tried the following WebFolder Values:
once you activated the http server included in Enterprise Browser, you can then set as start page the localhost on the configured port.
<WebServer> <Enabled VALUE="1"/> <Port VALUE="8082"/> <WebFolder VALUE="/XX/YY"/> <Public VALUE="0"/> </WebServer> <General> <Name value="Menu"/> <StartPage value="http://127.0.0.1:8082/index.html" name="my_app"/> <UseRegularExpressions value="0"/> </General>
From that point on you reference the other file from index.html with relatives path.
If the images are in the path /XX/YY/js, you reference it as:
Hope that this makes it a bit more clear :-)
Actually that didn't solve the problem, because I wasn't precise enough in describing the problem:
We are running a SAP mobile ITS server and we want to load local files from the device to improve the performance. Therefore using Webserver isn't the right thing.
I had the same problem with "not allowed..." in the internet explorer 6 mobile and solved it with changing the security zone in the registry. This made also the
Enterprise Browser with the IE Engine work with our service but not the EB with the Webkit engine.
Is there an entry in the registry for the security options of EB Webkit or another method to allow a website to load locally stored files?
Many thanks in advance and sorry for being not precise enough before
I don't know of any way to lower the standard security rules of the webkit rendering engine.
This behaviour is dictated by W3C standards and there are a couple of ways to work around Cross-Origin Resources:
- Application caches
My suggestion is to investigate HTML5 Application cache, that is supported by our Webkit rendering engine and you can use, adding a manifest to your webpages that states if the files can be cached on the local devices. In this way they're going to be downloaded from the server only once, and you can simply increse the version number of the resource in the Manifest file, when you need to distribute a new version of that resource.
You can find an intro on how to use app caches on HTML5 Rocks: A Beginner's Guide to Using the Application Cache - HTML5 Rocks.
Just pay attention to setup the correct MIME-Type for the Manifest file:
A manifest file must be served with the mime-type
text/cache-manifest. You may need to add a custom file type to your web server or