Welcome Guest Search | Active Topics | Sign In | Register

EO.WebBrowser: CACHE_READ_FAILURE Options
Riephi
Posted: Monday, March 8, 2021 5:09:50 AM
Rank: Advanced Member
Groups: Member

Joined: 7/17/2015
Posts: 51
Dear Support Team,

Sometimes we have problems launching our application in your WebBrowser.
After loading an URL via webview.loadUrl() nothing seems to happen. After looking up in DevTools we found some cache errors: CACHE_READ_FAILURE.
But only for a few ressources. Some ressources are load and some aren't load. The browser tries to load some ressources from cache, even if it's an inital loadUrl(). How could this be? Shouldn't the browser load all ressources from backend when the url is load inital after starting the application? Why does it try to read directly from cache at the first load?
After pressing F5 and refresh, all ressources are load completely.

We defined a custom cache directory: Runtime.DefaultEngineOptions.CachePath = CustomPath
First the read/ write permissions were not set for some users in the parent folder of this CustomPath, so we thought this was the cause. But after setting all authorizations and restart the engine the error also occurs. Manually clearing the cache folder did not help.

The error occurs in different versions of your WebBrowser: 20.3.34.0, 19.2.69.0, 18.3.46.0.

Do you know this cache issue? Or do you know how to fix it? Is there any way to ignore cache or clear cache every time before we call webView.loadUrl(), so that all ressources are newly load when calling webView.loadUrl()? Pressing F5 to refresh every time after loading a URL is not really an option.

Thanks in advance!

Best regards!
eo_support
Posted: Tuesday, March 9, 2021 2:42:40 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Hi,

This is how disk cache supposes work. It doesn't matter whether your application just freshly started. By default if you try to load a page and an unexpired version exists in cache the cached version will be used. So there is nothing wrong with your observed and there is nothing you can do to "fix" it.

Thanks
Riephi
Posted: Wednesday, March 17, 2021 8:53:25 AM
Rank: Advanced Member
Groups: Member

Joined: 7/17/2015
Posts: 51
Hi,

Thanks for your reply! We found out that there was a cache problem with our proxy. Adding some proxy exceptions did fix our problem.

Best regards!
eo_support
Posted: Wednesday, March 17, 2021 2:29:57 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,217
Great!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.