Header: location works in i.e. 9 but not in i.e. 11 - F12 says aborted?

we5inelgr

Greetings all,

I'm using this to manage timeout's:

if ($_SESSION['Timeout'] + 60 * 60 < time()) { //*   SESSION timeout - 1 hour (minutes * seconds) *//
  $_SESSION['Status'] = "1"; //* Use on signin page to display a message about timeout. *//
  session_write_close();
  header("Location: https://mysite.com/signin.html");
  exit;
}

This was working fine when I use I.E. 9.

I just upgraded I.E. to 11, and started testing with v 11. The code above remained the same, however, the page were this management code is doesn't redirect as it used to, just is blank (because of exit). I know the code above is being hit, as I can echo out something in there. So, it doesn't do the header redirect, but does hit the exit because the rest of the page code doesn't load (as expected).

Using F12, I can see in the Network panel that when I refresh the page, I get a Result of "(Aborted)." 😕

I've tried removing the "session_write_close();" (even though it works fine with I.E. 9), still doesn't redirect in I.E. 11.

I've also, since, tried using this:

header("Location: https://mysite.com/signin.html",TRUE,302);

but that too doesn't redirect in I.E.11.

Not sure what this means as far as what is "aborted" and why the page doesn't get redirected anymore with I.E. 11.

Ideas? 😕

dalecosp

I wonder if this note from an older KB (927917) has anything to do with it:

support.microsoft.com wrote:
Note Users may also receive this error message if a Web page in a Trusted Sites Zone sends a HTTP 302 redirect to a page in the Internet Zone. With protected mode, Internet Explorer 7 and later versions that are running on Windows Vista or a later operating system prevent redirects from Web pages that run at medium integrity to Web pages that run at low integrity for security reasons. In these scenarios, users may receive a similar "Operation Aborted" error message. To resolve this issue, make sure that HTTP 302 redirects are for pages within the same zone. For example, make sure that a redirect is from one Trusted Sites Zone page to another Trusted Sites Zone page. Or, make sure that both the source and the destination of the redirect don't involve a change in Internet Explorer's protected mode status.

Just a thought.... 🙁

we5inelgr

Interesting, and thanks for the repsonse!
In my case, the site is the same and both pages are on https.

https://mysite.com/pageWithTimeoutCheck.html

and

https://mysite.com/signin.html

So the trusted sites zone shouldn't be an issue here.