headers sent issue

[Platero]

Hi,
I've a stupid question but...

The code is the following:

if(($role!='tut or')&&(array_ke y_exists('tutor _id',$_GET)))
{
$possible_ids = array(2,6,7,8,9 ,10);
$t_id = $_GET['tutor_id'];

if(in_array($t_ id, $possible_ids)) {

$query="SELECT id_class FROM class WHERE
id_user='".$_GE T['tutor_id']."'";

$id_class=$db->get_field($que ry,id_class);

include("print_ data.php");

$formButtonLabe l = "Modifica";

}

--->else

{

//$my_echo = "hello";
//echo $my_echo;

//header('Locatio n: http://www.google.com' );
//exit();
}

}


What happens:

if in the array there's what you have in $_GET, anything works.

It's the else block that matters: :-)
- if I ONLY print $my_echo, no problems;
- if I comment $my_echo and I leave the header() uncommented, this
command doesn't work (that is, the page does not redirect);

What is happening?
How can I solve this?

I tried (in the else block) the headers_sent function too:

if (headers_sent() ) {
$my_echo = "sent";
echo $mioeco;
}

and it seems headers are sent, but maybe before I try to redirect.
Is there a way to "clean" the headers already sent??

Thanks very much,
Platero

[Rik]

Platero wrote:

I tried (in the else block) the headers_sent function too:

if (headers_sent() ) {
$my_echo = "sent";
echo $mioeco;
}

and it seems headers are sent, but maybe before I try to redirect.
Is there a way to "clean" the headers already sent??

No, once the headers are sent you're stuck with it. Remember: even a space
before <?php will result in headers being sent.

Headers must be sent before any output, whatever it is, wether it's
generated from php or fram a static file.

Grtz,
--
Rik Wasmus

[dawnerd]

Platero wrote:

Hi,
I've a stupid question but...

The code is the following:

if(($role!='tut or')&&(array_ke y_exists('tutor _id',$_GET)))
{
$possible_ids = array(2,6,7,8,9 ,10);
$t_id = $_GET['tutor_id'];

if(in_array($t_ id, $possible_ids)) {

$query="SELECT id_class FROM class WHERE
id_user='".$_GE T['tutor_id']."'";

$id_class=$db->get_field($que ry,id_class);

include("print_ data.php");

$formButtonLabe l = "Modifica";

}

--->else

{

//$my_echo = "hello";
//echo $my_echo;

//header('Locatio n: http://www.google.com' );
//exit();
}

}


What happens:

if in the array there's what you have in $_GET, anything works.

It's the else block that matters: :-)
- if I ONLY print $my_echo, no problems;
- if I comment $my_echo and I leave the header() uncommented, this
command doesn't work (that is, the page does not redirect);

What is happening?
How can I solve this?

I tried (in the else block) the headers_sent function too:

if (headers_sent() ) {
$my_echo = "sent";
echo $mioeco;
}

and it seems headers are sent, but maybe before I try to redirect.
Is there a way to "clean" the headers already sent??

Thanks very much,
Platero

Use output buffering, should fix your problem.

[Jerry Stuckle]

dawnerd wrote:

Platero wrote:

>>Hi,
I've a stupid question but...

The code is the following:

if(($role!='t utor')&&(array_ key_exists('tut or_id',$_GET)))
{
$possible_ids = array(2,6,7,8,9 ,10);
$t_id = $_GET['tutor_id'];

if(in_array($t_ id, $possible_ids)) {

$query="SELECT id_class FROM class WHERE
id_user='".$_ GET['tutor_id']."'";

$id_class=$db->get_field($que ry,id_class);

include("print_ data.php");

$formButtonLabe l = "Modifica";

}

--->else

{

//$my_echo = "hello";
//echo $my_echo;

//header('Locatio n: http://www.google.com' );
//exit();
}

}


What happens:

if in the array there's what you have in $_GET, anything works.

It's the else block that matters: :-)
- if I ONLY print $my_echo, no problems;
- if I comment $my_echo and I leave the header() uncommented, this
command doesn't work (that is, the page does not redirect);

What is happening?
How can I solve this?

I tried (in the else block) the headers_sent function too:

if (headers_sent() ) {
$my_echo = "sent";
echo $mioeco;
}

and it seems headers are sent, but maybe before I try to redirect.
Is there a way to "clean" the headers already sent??

Thanks very much,
Platero

Use output buffering, should fix your problem.

Better to find and fix the problem than unnecessarily add overhead by
buffering the output.

Output buffering has its uses. But to use it to get around a problem in
the code is not a good idea, IMHO.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[dawnerd]

Jerry Stuckle wrote:

dawnerd wrote:

Platero wrote:

>Hi,
I've a stupid question but...

The code is the following:

if(($role!='tu tor')&&(array_k ey_exists('tuto r_id',$_GET)))
{
$possible_ids = array(2,6,7,8,9 ,10);
$t_id = $_GET['tutor_id'];

if(in_array($t_ id, $possible_ids)) {

$query="SELECT id_class FROM class WHERE
id_user='".$_G ET['tutor_id']."'";

$id_class=$db->get_field($que ry,id_class);

include("print_ data.php");

$formButtonLabe l = "Modifica";

}

--->else

{

//$my_echo = "hello";
//echo $my_echo;

//header('Locatio n: http://www.google.com' );
//exit();
}

}


What happens:

if in the array there's what you have in $_GET, anything works.

It's the else block that matters: :-)
- if I ONLY print $my_echo, no problems;
- if I comment $my_echo and I leave the header() uncommented, this
command doesn't work (that is, the page does not redirect);

What is happening?
How can I solve this?

I tried (in the else block) the headers_sent function too:

if (headers_sent() ) {
$my_echo = "sent";
echo $mioeco;
}

and it seems headers are sent, but maybe before I try to redirect.
Is there a way to "clean" the headers already sent??

Thanks very much,
Platero

Use output buffering, should fix your problem.

Better to find and fix the problem than unnecessarily add overhead by
buffering the output.

Output buffering has its uses. But to use it to get around a problem in
the code is not a good idea, IMHO.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

I couldn't agree with you more. I find it always better to do all of
the dirty work before anything is outputted. IMO it's bad practice to
use PHP in the middle of html, unless it's used to output text.

Instead of say checking variables for errors and redirecting to a new
page in the middle of a page, do it before any html will even be
outputted, that way you are safe to set headers and the work.

[Platero]

Thanks very much.
I red all the thread and I solved :-)

Platero

[Mladen Gogala]

On Fri, 11 Aug 2006 23:26:44 -0400, Jerry Stuckle wrote:

Output buffering has its uses. But to use it to get around a problem in
the code is not a good idea, IMHO.

The whole business with headers is unnecessarily restrictive and real pain
in the neck or lower. Newer versions of Apache are more and more tolerant,
as they should be. If ob_start will solve my problem, I'll use it in a
heartbeat. It is a solution in 99% of the cases. For the remaining 1%,
it's still a pain.

--
http://www.mgogala.com

[Jerry Stuckle]

Mladen Gogala wrote:

On Fri, 11 Aug 2006 23:26:44 -0400, Jerry Stuckle wrote:

>>Output buffering has its uses. But to use it to get around a problem in
the code is not a good idea, IMHO.

The whole business with headers is unnecessarily restrictive and real pain
in the neck or lower. Newer versions of Apache are more and more tolerant,
as they should be. If ob_start will solve my problem, I'll use it in a
heartbeat. It is a solution in 99% of the cases. For the remaining 1%,
it's still a pain.

This not not an Apache restriction. It's one of the HTTP protocol, and
there isn't anything Apache can do to "fix" it.

And I understand. You're rather go for a "quick fix" than find and fix
the real problem.

Glad you're not on my team.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[Mladen Gogala]

On Sat, 12 Aug 2006 09:34:36 -0400, Jerry Stuckle wrote:

This not not an Apache restriction. It's one of the HTTP protocol, and
there isn't anything Apache can do to "fix" it.

I don't know, but I do see less problems with Apache 2.0.54 then with
Apache 1.0.3x. I haven't quantified anything

And I understand. You're rather go for a "quick fix" than find and fix
the real problem.

That does fix the real problem: unnecessary painful issue with "headers
already sent". If all that I want to do is to issue header() function and
redirect browser onto another page, then I don't really care about the
"real problem".

>
Glad you're not on my team.

No need to get personal here, but since you've put it that way, I too am
glad that I am not on your team.
--
http://www.mgogala.com

[Jerry Stuckle]

Mladen Gogala wrote:

On Sat, 12 Aug 2006 09:34:36 -0400, Jerry Stuckle wrote:

>>This not not an Apache restriction. It's one of the HTTP protocol, and
there isn't anything Apache can do to "fix" it.

I don't know, but I do see less problems with Apache 2.0.54 then with
Apache 1.0.3x. I haven't quantified anything

>>And I understand. You're rather go for a "quick fix" than find and fix
the real problem.

That does fix the real problem: unnecessary painful issue with "headers
already sent". If all that I want to do is to issue header() function and
redirect browser onto another page, then I don't really care about the
"real problem".

Nope. The real problem is why you're sending data in the first place.
There may be a valid reason. However, just using ob_start() just hides
the real problem.

>

>>Glad you're not on my team.

No need to get personal here, but since you've put it that way, I too am
glad that I am not on your team.

Yep, you wouldn't get away with that on my team. Like anything else -
you should have a reason for using ob_start(). And just using it to
hide the fact you've sent out something ahead of time - but have no idea
what you've sent - is not a valid reason.

Another case of a quick fix instead of finding the real problem. Sooner
or later it will come back to bite you.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===