|
|
Rank: Advanced Member
Groups: Member
Joined: 5/8/2015
Posts: 46
|
Hi,
Our application hosts an EO.WebBrowser control and a user often has multiple instances of our application running on the same PC, with the login sessions controlled by a cookie set on the local machine. We are seeing that since updating to EO.WebBrowser from the standard IE Web Browser control this is not possible.
After some investigation it looks like EO.WebBrowser is storing multiple cookies with the same key into the Cookies SqlLite DB.
I've opened the Cookies file in SqlLiteBrowser and can see multiple Cookies with the same name for the same host_key with different values.
I don't think this should be happening, I thought all instances of the web browser would use a single store if you set the Runtime.CachePath to the users local temp folder which we do).
Regards,
Andy.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Thank you very much for letting us know. We do not know all the details about this part yet since obviously all the cookie handling are done by the Chrome browser engine. We are under the impression that multiple instances should share the same cookie store too. We will look into this and see what we can find.
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/8/2015
Posts: 46
|
Hi,
I'd appreciate it if you could expedite this, we were under the impression it would be shared across all instances and our software cannot be used at the moment because of this issue.
Regards,
Andy.
|
|
Rank: Advanced Member
Groups: Member
Joined: 5/8/2015
Posts: 46
|
I should also mention that we have tested the same scenario running the normal Chrome web browser twice and it shares cookies fine so the problem if definitely in the EO control.
We are trying to produce a workaround for this issue by creating a custom cookie store but cannot seem to get that working either. We have implemented the BeforeSendHeaders event in the web view and try to set the value of the cookie manually or delete it but when run through Fiddler the request still has the same values as previously seen:
An update on this would be appreciated ASAP.
Regards,
Andy.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We have just replied your email on this issue. The reason that the normal Chrome browser works fine is because they use a single "browser" process. Chrome has a multiple process architecture that uses different child processes for different tasks. There is a separate process for each site and there is a single "browser" process that handles network traffic and also coordinates between other processes. For Chrome browser, no matter how many browser window you open, it always share a single "browser" process. Cookies are managed by the browser process. Since there is only one browser process no matter how many windows you open, so there will be no problem on cookie sharing.
In our current implementation we have the same model --- except that we have one browser process per your application instance. We plan to make this configurable so once that is done you will be able to share cookies.
Thanks!
|
|