Question

In an php-based application I’ve been coding, I have the following small block of code:

if (isset($_SERVER['QUERY_STRING'])) {
    header("Location: " . $_SERVER['QUERY_STRING']);
}

In my application, I use framesets and frames. This code is present in the main content area frame, and upon execution in IE, creates an infinite loop which kills the browser unless I manually stop loading.

The purpose of this code is to detect if there is a query string appended to the url, and if so, redirect to that query string. I’ve primarily been developing using chrome and and firefox, and today decided to test it in IE9. I have not tested it in any previous versions, but so far this behavior only occurs in IE, and I’m frankly stumped on why such is happening. I’ve searched for similar questions here and on the internet, but so far no dice.

Edit

As I noted with an earlier edit, I am using framesets and frames to control the interface. The left-hand frame, a side bar, contains links with a base target of the main ‘content’ area frame. The content of the content area frame contains javascript that appends a query string to the parent window’s url, so that when the index page is visited(with the query string present), it will redirect the content frame to that specific page.

This works perfectly fine in Chrome. Not IE(or firefox, which I just discovered as of this edit). Ie instead redirects to the index page, the page containing the frameset, and it does this forever, creating sidebar after sidebar.

Answer 1

I kind of hate myself for not thinking of this sooner, given how horribly simple it is. All I did, was check if $_SERVER['QUERY_STRING'] was empty, as so:

if (isset($_SERVER['QUERY_STRING']) && $_SERVER['QUERY_STRING'] != '') {
    header("Location: " . $_SERVER['QUERY_STRING']);
}

And that solved the problem of the index page creating infinite nested framesets and frames.