Comments on: PHP Redirect Vs JavaScript Redirect?

By: fyrye

fyrye — Wed, 31 Mar 2010 20:27:16 +0000

Since my previous post got cut off.
headers are not server side as the order of information goes.
Client Request->Server Serves (header)->Client receives (process header)->Client Request (Oh the page was moved to here?)->Server Serves.
Since the header function does not call for the information from the server.
For example header(“refresh: 1; url=/index.php”);
Is the same as the meta tag refresh example.
The difference is that the status and location headers are received by the client prior to meta tags (html)
A better example of server side redirect would be the include or require functions. In which the server requests the page to send to the client. And can not be blocked by the client like headers/scripts can be.

By: fyrye

fyrye — Wed, 31 Mar 2010 20:09:12 +0000

An alternative to the double header(“Location:”) and header(“http/1.1″) is to do
header(“Location:/”, true, 301);
Which translates to replace similar location headers with http-response 301 request client to be sent to web’s root.

Again remember headers can be manipulated, blocked, and disabled by the client.

By: Chaim Chaikin

Chaim Chaikin — Wed, 09 Dec 2009 00:29:28 +0000

The best idea for redirecting a user when a file has been moved, server side, is probably using htaccess file. You can use the PHP redirect when you want to check something first for example if you want to redirect a user to his account page after logging in.

By: sunilkumar

sunilkumar — Mon, 16 Nov 2009 05:54:26 +0000

Its really a good post. Thanks for posting.

By: Emile

Emile — Fri, 30 Oct 2009 11:19:50 +0000

A very important difference is when redirecting from https to http:
header() will give a warning in a popup window in the browser
location.replace(…) will do the redirect without a warning