Logo
My Account |  Site Map | Contact Us  
Welcome Guest Search | Active Topics | Sign In | Register

Cookies save issue Options
AiSatan
Posted: Tuesday, December 5, 2017 11:16:43 AM
Rank: Advanced Member
Groups: Member

Joined: 2/11/2016
Posts: 31
Previous messages


Quote:
Can you try the same with Google Chrome browser and see if it behaves the same? If Google Chrome behaves the same, then we will usually wait for the Chromium team to address it first as we are not in a position to fix browser engine issues because it is extremely large and complex, so it is not possible for us to address those issues on our end.


I've tested with latest Chrome, work fine.
I've even tried kill the chrome process immediately, but all work fine.


Quote:
Another possibility is it may indeed takes that long for the cookies to be received by the client. You can add some code inside the WebView's AfterReceiveHeaders event to trace the cookies that you received. If the server does not send the authentication cookie down right away, then obviously that can only be addressed on the web server side. If you do see the cookies have been sent down right away and Google Chrome does not show this time delay, please PM us with a test page and we will be happy to investigate further.


So, I see that auth_token and others came with new twitter page.

My test application code (as I said, I tried in TabBrowser too):

Code: C#
public CreateWebView()
        {
            wv = new WebView();
            wv.AfterReceiveHeaders += WvOnAfterReceiveHeaders;
            wv.Create(Handle);
            wv.LoadUrlAndWait("https://twitter.com");
            InitializeComponent();
        }

        private void WvOnAfterReceiveHeaders(object sender, ResponseEventArgs responseEventArgs)
        {
            foreach (var key in responseEventArgs.Response.Cookies.AllKeys)
            {
                Console.WriteLine($"Cookie: {key}");
            }
        }


Quote:
Output:

Cookie: fm
Cookie: _twitter_sess
Cookie: personalization_id
Cookie: guest_id
Cookie: ct0
Cookie: fm
Cookie: _twitter_sess
Cookie: metrics_token
Cookie: test_cookie
Cookie: test_cookie
Cookie: IDE
Cookie: fm
Cookie: ads_prefs
Cookie: kdt
Cookie: _twitter_sess
Cookie: remember_checked_on
Cookie: twid
Cookie: auth_token



Please, try this steps with TabBrowser:

1) navigate to https://twitter.com
2) log in
3) wait while new page will be fully load(After it, you can even navigate to the next page in twitter and all will be ok)
4) close browser
5) try open twitter again


Thanks.
AiSatan
Posted: Thursday, December 7, 2017 9:12:42 AM
Rank: Advanced Member
Groups: Member

Joined: 2/11/2016
Posts: 31
Can somebody answer me, please?
eo_support
Posted: Thursday, December 7, 2017 2:41:22 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 19,843
Hi,

Sorry about the delay. We have been trying to reproduce this problem but have not been able to.

We have tried exactly the steps you described above. More clarification:

Step 3: We waited as soon as the account name is displayed;
Step 4: We closed the TabbedBrowser sample application;
Step 5: We relaunched the TabbedBrowser sample application and typed in twitter.com in the address bar again, then hit enter. The page loaded as logged in;

If you still have problems, it may be related to some other third party application on your system and you can try on a different system to see if it works for you. The cookies are saved in the current user's Temp directory under "eo.webbrowser.cache.xxxx" where "xxxx" is the version number. So make sure you do not have any third party application that interferes with this directory.

Thanks


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.