Welcome Guest Search | Active Topics | Sign In | Register

Conflict between webView CertificateError Options
hmireault
Posted: Wednesday, July 16, 2014 8:57:17 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 52
Hello again,

The way our program works, we can have two or more different webView + webControl objects in different tabs. When the CertificateError event happens for one of the webViews, and the e.Continue() method is called, it seems to also affect the other webView object, making the CertificateError event not happen again for either webViews. This is normal for the one whose CertificateError event got handled properly, but it doesn't seem normal for the other CertificateError event.

Basically, is it normal that doing e.Continue() in the CertificateError event of one webView affects the CertificateError event of another webView? Is this a bug? Is there a way around it?

Thanks in advance.
eo_support
Posted: Thursday, July 17, 2014 5:19:35 PM
Rank: Administration
Groups: Administration

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

We have looked into this issue. The reason that it works this way is because the browser engine stores a map of <host, certificate, ignore_state>. If a certificate error is acknowledged and accepted (this is what e.Continue() does), it won't be prompted again. This does make sense with a normal web browser since a browser does not want to ask the user again and again for the same error. If this map did not exist, then the browser will be asking user again and again not only for multiple pages from the same site, but for multiple resource requests (JavaScript, styles, images, etc) within the same page. Obviously the later would not be acceptable from the user's point of view. Since our product is directly based on Chrome's source code, we inherited this logic as well.

Thanks!
hmireault
Posted: Friday, July 18, 2014 8:28:43 AM
Rank: Advanced Member
Groups: Member

Joined: 7/14/2014
Posts: 52
I definitely understand the logic, although I would have thought it would be separated if it was a different webView+webControl. Luckily for us, though, it has a very minor impact in the functions of our application.

Thank you very much for the quick reply!


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.