PHP script stops when page redirected

CHsurfer

I have a page that is acting strangely. This page checks session variables to see if the user is logged in. If not, a login form is shown. The user can fill in the form, which goes to a background page that does the validation and database check. If the login is successfull, session vars are set and the page is redirected back to the original page. Here, the php script in the beginning executes, but stops at the first '?>'. If you reload the page from here, the page displays normally, including all of the normal HTML code after the initial stopping point. Any ideas why this might be happening?

Another interesting point is that when I try to 'view sourceocode' of the incomplete page in the browser, nothing happens.

Thanks,

Jon

<?php
    error_reporting(E_ALL); 
    session_start();
    include 'inc.php';
    ////var_dump($_SESSION);

//var_dump($_SESSION);
//var_dump($http_response_header);
var_dump($_GET);
var_dump($_POST);
var_dump($_COOKIE);
//****The coad stops executing here when called from a redirect.************
?>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>Video Niche Main Page</title>
    </head>
    <body>
    <h1>Welcome to ...

etully

Lots of people have looked at this question but nobody has answered which means that we're all stumped, just like you. When I find myself in that situation, I start removing stuff to see if I can isolate which part is causing the problem. The other thing I do is to start injecting print statements so that I can trace which parts of the code are successfully getting executed.

Other than the session_start() and the include() statements, there are four commands (one that turns on error checking and three var_dumps). I suggest commenting them all out just during the troubleshooting phase. This way, you can remove them as possible suspects. (Not that they are suspects - they should be fine, but get rid of them anyway).

Then do this: Put a print "1"; and a print "2"; just before and just after the include() statement like this:

    session_start();
    print "1";
    include 'inc.php';
    print "2";

If you see a "1" but not a "2", then you know that the execution is stopping somewhere inside the include() statement. I'm going to guess that for some reason (which we can't see here because we don't have the code for inc.php), the execution is stopping inside inc.php. Maybe there's an error which isn't showing up (even though you have errors set to E_ALL). I mean, it's not likely, but when you're stumped, you grasp at straws, test everything, make no assumptions.

Hopefully, more print statements will shed light on what's going on.