|
|
Rank: Newbie
Groups: Member
Joined: 6/17/2015
Posts: 6
|
I'm currently evaluating EO Webbrowser as a replacement to .net WebBrowser control. Trying to handle navigation errors like site being down but I cannot get LoadFailed to fire at all.
I even created a test project that does a LoadUrl to a page that doesn't exist (404) and I only get LoadComplete event firing. Am I doing something wrong?
Trial version 3.0.112.0
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Please check e.Task.HttpStatusCode in your LoadCompleted event handler. LoadFailed is only fired when there is protocol level failure (for example, domain name can not be resolved). A 404 is considered a completed load since the HTTP conversation completed without any error. To verify it indeed completed a normal load, verify HttpStatusCode to be 200.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/17/2015
Posts: 6
|
e.Task.HTTPStatus code is 0 and so is the error code. I get the same result when I shut down my development web server to simulate internet being down. It's even 0 on a successful page load
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Please use the latest version (3.0.113). This build specifically fixed the HttpStatusCode issue.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 6/17/2015
Posts: 6
|
Not only did that fix the HttpStatusCode, it actually causes the LoadFailed event to fire. Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Ah. That proves my understand was wrong. :) Thanks for the update!
|
|