Open mmuellersk opened 10 years ago
It maybe a bug in IE11 on Windows 8.1. But I do not have Windows 8.1, so can not test on that.
Might be worth using SauceLabs for testing: https://saucelabs.com/platforms
We are having the same issue in IE11 and Win 8.1. Any workarounds or ways to fix it?
We have the following scenario: Middleware initialization: app.configure(function() { ... app.use(clientSession({ cookieName: 'userinfo', secret: 'SOME_SECRET', cookie: { domain: '.mydomain.ch' } })); ... });
Later we only use the userinfo attribute on the request object. On all browser this works fine. Except: IE 11 (11.09600.176239), Windows 8.1: NOT WORKING IE 11 (11.09600.17207), Windows 7: OK (The configuration of IE on windows 7 and Windows 8.1 is the same (authorize cookies...)) Chrome, Windows 8.1: OK
By analyzing the network traffic it turned out that the auth. request returned a set cookie in the response as follows:
Set-Cookie: userinfo=<>; path=/; expires=Wed, 03 Sep 2014 09:09:46 GMT; domain=.mydomain.ch; httponly
All subsequent request do not contain the session cookie. So we get only 401 after the authentification. By analyzing the server logs it turned out that the auth. on the server side worked fine. Actually for some reason IE 11 on Windows 8.1 do not return the session cookie.
Can you reproduce this issue? Is there is something wrong with our middleware initialization? Is this is a bug in IE11 on Windows 8.1?
Just in case: we use a https connection for this server. In front of the node js application is a nginx server. The https channel ends in the nginx server (no ssl in node js application)
Please advise.