Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Frans de Jong 319 posts 1012 karma points c-trib
    Mar 12, 2018 @ 09:14
    Frans de Jong
    0

    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?

  • Michaël Vanbrabandt 756 posts 2934 karma points c-trib
    Mar 12, 2018 @ 09:31
    Michaël Vanbrabandt
    0

    Frans,

    any errors in the log or in the error console of the IE browser?

    /Michaël

  • Frans de Jong 319 posts 1012 karma points c-trib
    Mar 12, 2018 @ 09:32
    Frans de Jong
    0

    No errors at all. Thats the strange thing.

  • Frans de Jong 319 posts 1012 karma points c-trib
    Mar 12, 2018 @ 09:35
    Frans de Jong
    0

    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.

  • Michaël Vanbrabandt 756 posts 2934 karma points c-trib
    Mar 12, 2018 @ 09:42
    Michaël Vanbrabandt
    0

    Any firewalls or virus scanners in place?

    /Michaël

  • Frans de Jong 319 posts 1012 karma points c-trib
    Mar 12, 2018 @ 09:43
    Frans de Jong
    0

    On the client pc or server?

  • Michaël Vanbrabandt 756 posts 2934 karma points c-trib
    Mar 12, 2018 @ 09:46
    Michaël Vanbrabandt
    0

    Client PC

  • Frans de Jong 319 posts 1012 karma points c-trib
    Mar 12, 2018 @ 11:15
    Frans de Jong
    0

    Nope, I'm testing with a clean install.

  • Frans de Jong 319 posts 1012 karma points c-trib
    6 days ago
    Frans de Jong
    100

    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.

Please Sign in or register to post replies

Write your reply to:

Draft