We have some strange behaviour with a site on Windows 8.1 IE11.
All other browsers and IE 11 on windows 10 work ok.
The issue we are experiancing is that we can't log in to umbraco and if the site runs for more than +/- 5 minutes it becomes unreachable.
When we are using HTTP instead of HTTPS the site is always reachable.
We've tested a static html to and that has no issues on Https.
Will try a blank Umbraco install next.
Issue is sort of resolved. A unknown event broke our code that tried to add a cookie and it added the addcookie header a couple of hundred times in the response header. After this event occurred in IE it was also visible in Chrome.
This issue wasn't reproducible with any other combination of url, certificate, or server.
We solved it by clearing all add cookie directives in the response header as late as possible and setting the cookie if needed after that point.
Site unreachable Windows 8.1 IE11
Hi all,
We have some strange behaviour with a site on Windows 8.1 IE11. All other browsers and IE 11 on windows 10 work ok.
The issue we are experiancing is that we can't log in to umbraco and if the site runs for more than +/- 5 minutes it becomes unreachable. When we are using HTTP instead of HTTPS the site is always reachable.
We've tested a static html to and that has no issues on Https. Will try a blank Umbraco install next.
Any ideas on what it could be?
Frans,
any errors in the log or in the error console of the IE browser?
/Michaël
No errors at all. Thats the strange thing.
Maybe there are errors when trying to log in but the main issue is the site being unreachable.
I'll check for errors in a minute. We are doing multiple tests right now.
Any firewalls or virus scanners in place?
/Michaël
On the client pc or server?
Client PC
Nope, I'm testing with a clean install.
Issue is sort of resolved. A unknown event broke our code that tried to add a cookie and it added the addcookie header a couple of hundred times in the response header. After this event occurred in IE it was also visible in Chrome.
This issue wasn't reproducible with any other combination of url, certificate, or server.
We solved it by clearing all add cookie directives in the response header as late as possible and setting the cookie if needed after that point.
So no clear cause but issue solved anyway.
is working on a reply...