![]() ![]() Of course, server side investigations have no sense if others browsers are running flawlessly in a significant number. ![]() Session storage could also be a clue (quite low chance though except if the "no returned session cookie" request is the consequence of a previous unlogged invalid cookie kicking). What about server side ? Load balancers can be an explanation. Have you also tried to tweak a bit the cookie name and content ( remove domain for instance if feasible in your subdomain context) ? Have you managed to check if the cookie is still been registered client side before/after the faulty request ? Have you check the request headers client side ? The question is about Edge forgetting the cookie itself, Edge forgetting to send the cookie, Edge sending a bad cookie.When you say it's ok in other browsers, is it based on some test cases or Edge is only one of the many browsers usually employed ?.I have so many questions and thoughts that it will be too long for a comment : 09:46:21 UTC 200 hasIdentity: 0 UserId: 0 Response headers: Array 09:46:21 UTC GET hasIdentity: 0 UserId: 0 Request: / Cookie: _gid=redacted _ga=redacted prefLang=de app=redactedXYZ => Set-Cookie: app=redactedXYZ path=/ domain= secure HttpOnly 09:46:21 UTC 302 hasIdentity: 0 UserId: 0 Response headers: Array 09:46:21 UTC POST hasIdentity: 0 UserId: 0 Request: / Cookie: _gid=redacted _ga=redacted prefLang=de => Cache-Control: no-store, no-cache, must-revalidate 09:44:00 UTC 200 hasIdentity: 0 UserId: 0 Response headers: Array the user opens an iframe with a page request from the same originĮxample with request/response debug information server side where the session cookie app=redactedABC is not transmitted to the server 09:44:00 UTC POST hasIdentity: 1 UserId: Request: / Cookie: _gid=redacted _ga=redacted app=redacted-ABC prefLang=de.immediately within seconds of page requests.More than 12mins have been passed between page requests within the app context.The user opens an externally linked page from the loggedin app context with target=_blank.The dropping occures is not easily reproducible but has been visible sometimes when: The mentioned "prefLang" cookie is not dropped and is visible on the server. In some cases, MS Edge simply drops the session cookie named "app" and is not part of the HTTP request any longer. The cookies are HttpOnly, secure and set only for the actual subdomain in use. Other cookies involve storing a the current display language with a cookie name of "prefLang". Our users are authenticated via a session cookie. The same issue does not happen on IE 11/Chrome/Firefox. We're experiencing a strange behaviour on MS Edge with at least versions 16/17. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |