Php header location redirect not working

This is likely a problem generated by the headers being already sent.

Why

This occurs if you have echoed anything before deciding to redirect. If so, then the initial (default) headers have been sent and the new headers cannot replace something that’s already in the output buffer getting ready to be sent to the browser.

Sometimes it’s not even necessary to have echoed something yourself:

  • if an error is being outputted to the browser it’s also considered content so the headers must be sent before the error information;
  • if one of your files is encoded in one format (let’s say ISO-8859-1) and another is encoded in another (let’s say UTF-8 with BOM) the incompatibility between the two encodings may result in a few characters being outputted;

Let’s check

To test if this is the case you have to enable error reporting: error_reporting(E_ALL); and set the errors to be displayed ini_set('display_errors', TRUE); after which you will likely see a warning referring to the headers being already sent.

Let’s fix

Fixing this kinds of errors:

  • writing your redirect logic somewhere in the code before anything is outputted;
  • using output buffers to trap any outgoing info and only release it at some point when you know all redirect attempts have been run;
  • Using a proper MVC framework they already solve it;

More

MVC solves it both functionally by ensuring that the logic is in the controller and the controller triggers the display/rendering of a view only at the end of the controllers. This means you can decide to do a redirect somewhere within the action but not withing the view.

Leave a Comment