Hello,
Sorry about the delay. We are not familiar with details of NTLM authentication. However we were able to debug into Chromium's source code and found out that it fails at line 380 in the following file:
https://cs.chromium.org/chromium/src/net/http/http_auth_sspi_win.ccThis would result in LoadFailed event being triggered with error code ERR_UNEXPECTED, which is the equivalent of ErrorCode.UnexpectedError on the .NET side. As such to workaround this error, you can handle the WebView's LoadFailed event and reload the Url. For example, with the following code based on our TabbedBrowser sample application:
Inside NewWebViewItem function:
Code: C#
//Attach the event handler
item.Page.WebView.LoadFailed += WebView_LoadFailed;
The event handler:
Code: C#
private void WebView_LoadFailed(object sender, LoadFailedEventArgs e)
{
if (e.ErrorCode == ErrorCode.UnexpectedError)
{
EO.WebBrowser.WebView webView = (EO.WebBrowser.WebView)sender;
Dispatcher.BeginInvoke(new Action(() =>
{
webView.Url = e.Url;
}));
}
}
Note that:
1. You must use Dispatcher.BeginInvoke to delay the reload since you must allow the first load cycle to complete;
2. You may want to add code to limit the reload to only once to avoid an infinite reload loop due to other unknown scenarios;
Hope this helps.
Thanks!