Bug #53818
closed
Internet Explorer 11 BE Cookies problem
Added by Vladimir Kubak over 10 years ago. Updated over 5 years ago.
100%
Description
Accessing backend with Internet Explorer 11 causes "Activate Cookies, please" message, instead of login form. Cleaning cookies causes login page appears for the first time. Then again...
IE 11 on Windows 7 - tested on 3 different computers - 32 and 64bit, different locations.
Tested on our 4.5 and 4.7 instalations and also on introduction.typo3cms.demo.typo3.org.
Tried different settings of IE with no luck.
Files
| Cookies_activate.png (87.6 KB) Cookies_activate.png | Wouter Wolters, 2013-11-21 10:44 |
Updated by Markus Klein over 10 years ago
- Category set to Backend User Interface
- Status changed from New to Accepted
- Target version set to next-patchlevel
- Complexity set to medium
So the login basically works right?
I tested this on 4.5, 4.7 and 6.1 now and everywhere the same behaviour.
But there's a link below saying "Ignore ...".
This allows to login as normal.
Updated by Wouter Wolters over 10 years ago
- File Cookies_activate.png added
I can also reproduce this. Attached screenshot will be shown.
The first login to the site works. After you visit the site again and try to login the screen pops up.
Updated by Wouter Wolters over 10 years ago
- File Cookies_activate.png Cookies_activate.png added
Updated by Ernesto Baschny over 10 years ago
Does that also happen on current "master" (6.2 development)? I ask because we added the "X-UA compatibility" flag there to make IE know that the backend is "IE10 compatible" (used to be IE9). Maybe this affects this particular scenario?
Updated by Vladimir Kubak over 10 years ago
Markus Klein wrote:
So the login basically works right?
I tested this on 4.5, 4.7 and 6.1 now and everywhere the same behaviour.
But there's a link below saying "Ignore ...".This allows to login as normal.
Right, but some of our editors are confused. They still call...
Updated by Wouter Wolters over 10 years ago
Ernesto Baschny wrote:
Does that also happen on current "master" (6.2 development)? I ask because we added the "X-UA compatibility" flag there to make IE know that the backend is "IE10 compatible" (used to be IE9). Maybe this affects this particular scenario?
Ernesto that was also what I thought so I directly tried my dev-system at work. But this also happens on 6.2:(
Updated by Stefan Neufeind over 10 years ago
relevant part is in typo3/sysext/t3skin/Resources/Public/JavaScript/login.js:
checkCookieSupport: function() {
Ext.util.Cookies.set('typo3-login-cookiecheck', true);
cookieEnabled = Ext.util.Cookies.get('typo3-login-cookiecheck');if (!cookieEnabled) {
TYPO3BackendLogin.showCookieWarning()
}Ext.util.Cookies.clear('typo3-login-cookiecheck');
},Could there be a reason why IE11 does not accept this cookie? Wrong cookie-path or so?
Updated by Stefan Neufeind over 10 years ago
I just found out that with a "normal" browser the user/password-fields would show again. But with IE11 on the error-page they are gone for me. So maybe there is some HTML-error preventing the cookie-check from running at all and/or the boxes from being hidden using CSS.
Updated by Stefan Neufeind over 10 years ago
ah no, the fields are hidden by showCookieWarning() - hmm ...
Updated by Gerrit Code Review over 10 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25852
Updated by Stefan Neufeind over 10 years ago
- Status changed from Under Review to Accepted
The debugger-console of IE11 showed that on a call to clear() and another set() when running the next cookie-check actually two cookies were set. The get() from ExtJS however would return the first one (being empty) instead of the most current one that holds "true" from the cookie-check.
This forum-post also suggests that clear() from ExtJS for cookies does not work correctly:
http://www.sencha.com/forum/showthread.php?98070-Ext.util.Cookies.clear%28%29-not-working&p=462560#post462560
The problem might be that clear() tries to "set" a cookie but with different values.
Workaround: Instead of calling clear() use set() and specify a date in the past (actually the same way as clear() would do it). This way the same settings for the cookie will be used.
Using the debugger in IE11 you can see that the cookie is immediately gone after this pseudo-clear was executed.
Updated by Gerrit Code Review over 10 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch TYPO3_6-1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25868
Updated by Gerrit Code Review over 10 years ago
Patch set 1 for branch TYPO3_6-0 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25869
Updated by Gerrit Code Review over 10 years ago
Patch set 1 for branch TYPO3_4-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25870
Updated by Gerrit Code Review over 10 years ago
Patch set 1 for branch TYPO3_4-5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25871
Updated by Stefan Neufeind over 10 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset ae944d90197bfae63a02faff74a80d98bf061bb2.
Updated by Gerrit Code Review over 10 years ago
- Status changed from Resolved to Under Review
Patch set 2 for branch TYPO3_6-1 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25868
Updated by Gerrit Code Review over 10 years ago
Patch set 2 for branch TYPO3_6-0 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/25869
Updated by Stefan Neufeind over 10 years ago
- Status changed from Under Review to Resolved
Applied in changeset 28ca149e589f6623e59ac009572cc1b15b9084e0.
Updated by Miroslaw Kmiec about 10 years ago
in typo3/sysext/t3skin/Resources/Public/JavaScript/login.js in line 166 schould be, for ex.:
Ext.util.Cookies.set('typo3-login-cookiecheck', true, time () + 60000);
set() should be with 3 parameters to fix IE problem
Updated by Jorgo S. about 10 years ago
Not resolved, I still have this problem in TYPO3 6.1.7 and IE11.
Updated by Stefan Neufeind about 10 years ago
Was merged to 6.1 right after release of current 6.1.7 :-(
Review for 6.1-tree: https://review.typo3.org/25868
Please grab the fix from there and try it out.
Updated by Jorgo S. about 10 years ago
I checked, I had already patched it, so unfortunately something's still wrong.
Updated by Stefan Neufeind about 10 years ago
Did you clear cookies and/or maybe completely closed IE11 after patching? Using the F12-developertool from IE I was able during debugging to see that two cookies actually existed. With the patch the same one is set and unset in both cases. But once something went wrong (without the patch) the problematic cookie is there and won't go away itself unfortunately.
Updated by Jorgo S. about 10 years ago
Yes, silly me. Cleared Cookies again and no more problems so far.
Updated by 