Cookies not permanently found in all tabs in IE

There was a rather strange problem, I'm sure that this is the browser setting, so although this is not a programming problem, I was wondering if people came across it during their development and could offer a solution / reason.

My application is located in MVC 2 and launches a central menu system with links to real application screens, all of which have a goal = "_ blank" and open either in new windows or in new tabs depending on how the user prefers through his settings browser. All this works fine in every system in which we use it, in addition to the new one - we create a new Citrix desktop, and when testing we get strange behavior. We can log in, normally, and navigate the menu, but when we get to the menu, 90% of the time when a new link opens with a login call, as if the browser no longer has a session cookie. However, when we return to the main tab, we are still logged in and can navigate the menu well. Another very strange thing is that from time to time I can load the screen in a new tab and start it in order, but then open it again from the menu, and we again receive a login request. As soon as I sign up for one new tab, the rest will open normally, which is even more strange.

I assume this is some kind of tab isolation isolation, but since it doesn't always work. if so, is it known that it is a little buggy? The IE 8 browser that we use on all other systems is excellent. Any group policy settings that may be causing this, as it happens when a user logs in with whom we are testing but not washing - I am waiting for our network administrator to come back to me regarding any differences between administrators and users, but I thought what will I ask here if he does not see anything obvious.

Cheers - MH

+4
source share
1 answer

It turns out that this is an IE error (not surprising there) - when the browser creates a new tab in a new workflow, the new process does not have access to the session file. Several other people found this and stopped breeding new processes, although not a great solution, it seems to fix the problem. Please note that this issue also occurs on the Yahoo website and on all other sites using session cookies. Actually, I’m not sure which combination of events and situations causes this (only non-administrators get into our system - we looked at our GPO rules but didn’t find anything obvious), but I believe that MS really needs to fix this. because if it starts to fire more often, it can completely destroy IE.

Here is a link to a temporary workaround for the problem if you get into it yourself.

http://blogs.msdn.com/b/askie/archive/2009/03/09/opening-a-new-tab-may-launch-a-new-process-with-internet-explorer-8-0. aspx

+2
source

Source: https://habr.com/ru/post/1439795/


All Articles