Yes, if you code properly it is easy to use header() and other functions like session_start() and setcookie() which requires that no output would be send before they are called, as a matter of fact it is best to output your site at the end of script after everything has been execute, but an alternative to this is to use output buffering, earlier a lot of whom did not use it, because they were "afraid" that something might be wrong and were avoiding ob_start() function, but a lot of whom saw the potential to use it and saw that everything works clean, I use it myself and now I usually don't have problems with it, but you need to get used to it and use it properly too.

and sometimes using the Refresh header, which brakes the back button is good, especially if you want to break it and that users could not browse back to them and you can use it not only by meta tags, it is the same with header() function:



And the code can continue if you want it to parse something, just add some more seconds for the header, the browser will redirect. But remember, that Refresh header is not the Standard of HTTP, Most browsers just support it and thats all, so be careful when using it, the alternative is to use flush() with sleep() but this is crazy.

Reply

The best way to do it is to send the redirection status code for the HTTP/1.1 protocol (3XX) which automatically gets sent when using the PHP header('Location: someaddress/page') function, unless a status code has already been sent. The meta refresh is not a good idea, because it breaks the back button.

Status code 301 for permanent redirect or Status code 302 for temporary.



Should always make sure to exit too, incase there's code after it that you don't want to process before being redirected. There's other ways to do it too, which requires .htaccess file and URL rewriting or using the redirect derivative but avoid using meta refresh.


Cheers,


MC

Reply