Re: using meta http-equiv in php

Greetings, Jerry Stuckle.
In reply to Your message dated Monday, March 31, 2008, 01:57:38,

> AnrDaemon wrote:
>> Greetings, Michael Fesser.
>> In reply to Your message dated Monday, March 10, 2008, 03:07:19,
>>
>>> .oO(ajtrichards@googlemail.com)
>>
>>>> You should use something like:
>>>>
>>>> header('Location: thankyou.php');
>>>> die();
>>
>>> Besides the missing scheme and hostname - this was what the OP was
>>> trying, but there was some output _before_ the header() call.
>>
>> And according to PHP specification, "Location" header must contain fully
>> qualified address, including protocol identificator and host name.
>>
>> BTW, nothing wrong in sending some output before header() call... if You
>> REALLY know what You doing. That all depends on Your host configuration.
>>
>>

> Wrong. From the PHP manual under the header function:

> "Remember that header() must be called before any actual output is sent,
> either by normal HTML tags, blank lines in a file, or from PHP."

> You CANNOT send output before a header() call. And don't try to claim
> you can use ob_start(), etc. That just masks the problem, not solves it.

die(0);


--
Sincerely Yours, AnrDaemon

Re: using meta http-equiv in php

AnrDaemon wrote:
> Greetings, Jerry Stuckle.
> In reply to Your message dated Monday, March 31, 2008, 01:57:38,
>
>> AnrDaemon wrote:
>>> Greetings, Michael Fesser.
>>> In reply to Your message dated Monday, March 10, 2008, 03:07:19,
>>>
>>>> .oO(ajtrichards@googlemail.com)
>>>>> You should use something like:
>>>>>
>>>>> header('Location: thankyou.php');
>>>>> die();
>>>> Besides the missing scheme and hostname - this was what the OP was
>>>> trying, but there was some output _before_ the header() call.
>>> And according to PHP specification, "Location" header must contain fully
>>> qualified address, including protocol identificator and host name.
>>>
>>> BTW, nothing wrong in sending some output before header() call... if You
>>> REALLY know what You doing. That all depends on Your host configuration.
>>>
>>>
>
>> Wrong. From the PHP manual under the header function:
>
>> "Remember that header() must be called before any actual output is sent,
>> either by normal HTML tags, blank lines in a file, or from PHP."
>
>> You CANNOT send output before a header() call. And don't try to claim
>> you can use ob_start(), etc. That just masks the problem, not solves it.
>
> die(0);
>
>

Which doesn't allow the header() call to be sent, among other things.

And even then, it doesn't guarantee the headers have NOT been sent already.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Re: using meta http-equiv in php

Greetings, Jerry Stuckle.
In reply to Your message dated Monday, March 31, 2008, 21:26:13,

>>>>>> You should use something like:
>>>>>>
>>>>>> header('Location: thankyou.php');
>>>>>> die();
>>>>> Besides the missing scheme and hostname - this was what the OP was
>>>>> trying, but there was some output _before_ the header() call.
>>>> And according to PHP specification, "Location" header must contain fully
>>>> qualified address, including protocol identificator and host name.
>>>>
>>>> BTW, nothing wrong in sending some output before header() call... if You
>>>> REALLY know what You doing. That all depends on Your host configuration.
>>>>
>>>>
>>
>>> Wrong. From the PHP manual under the header function:
>>
>>> "Remember that header() must be called before any actual output is sent,
>>> either by normal HTML tags, blank lines in a file, or from PHP."
>>
>>> You CANNOT send output before a header() call. And don't try to claim
>>> you can use ob_start(), etc. That just masks the problem, not solves it.
>>
>> die(0);
>>
>>

> Which doesn't allow the header() call to be sent, among other things.

> And even then, it doesn't guarantee the headers have NOT been sent already.


That was order for Your death. You're just a disturbance and thinking that
only Your point of view is right. So, please die without raising any
errorlevels.

I cannot send any output to the user when I have output buffering enabled
(unless I use explicit ob_flush() call). What I mean "If You know what You
doing". And I'm surely know what I doing by zipping output to help ppl get my
pages quickly and successfully.

I was not very precise in my words using "sending" instead of "printing", and
I apologise for that to the rest of newsgroup.

End of statement.


--
Sincerely Yours, AnrDaemon

Re: using meta http-equiv in php

Greetings, Jerry Stuckle.
In reply to Your message dated Thursday, April 3, 2008, 02:32:32,

>>>>>>>> You should use something like:
>>>>>>>>
>>>>>>>> header('Location: thankyou.php');
>>>>>>>> die();
>>>>>>> Besides the missing scheme and hostname - this was what the OP was
>>>>>>> trying, but there was some output _before_ the header() call.
>>>>>> And according to PHP specification, "Location" header must contain fully
>>>>>> qualified address, including protocol identificator and host name.
>>>>>>
>>>>>> BTW, nothing wrong in sending some output before header() call... if You
>>>>>> REALLY know what You doing. That all depends on Your host configuration.
>>>>>>
>>>>>>
>>>>> Wrong. From the PHP manual under the header function:
>>>>> "Remember that header() must be called before any actual output is sent,
>>>>> either by normal HTML tags, blank lines in a file, or from PHP."
>>>>> You CANNOT send output before a header() call. And don't try to claim
>>>>> you can use ob_start(), etc. That just masks the problem, not solves it.
>>>> die(0);
>>>>
>>>>
>>
>>> Which doesn't allow the header() call to be sent, among other things.
>>
>>> And even then, it doesn't guarantee the headers have NOT been sent already.
>>
>>
>> That was order for Your death. You're just a disturbance and thinking that
>> only Your point of view is right. So, please die without raising any
>> errorlevels.
>>
>> I cannot send any output to the user when I have output buffering enabled
>> (unless I use explicit ob_flush() call). What I mean "If You know what You
>> doing". And I'm surely know what I doing by zipping output to help ppl get my
>> pages quickly and successfully.
>>
>> I was not very precise in my words using "sending" instead of "printing", and
>> I apologise for that to the rest of newsgroup.
>>
>> End of statement.

> Good programmers fix errors. Sloppy programmers hide them with thinks
> like ob_start().

It is not hiding and it is not an error. It is usage of proper tools the right
way to achieve given goals.
I do not want to break program logic in the favor of Your "good programming".
Call it bad logic, but it is more clear, than Your goodness. So far.


--
Sincerely Yours, AnrDaemon

Re: using meta http-equiv in php

AnrDaemon wrote:
> Greetings, Jerry Stuckle.
> In reply to Your message dated Monday, March 31, 2008, 21:26:13,
>
>>>>>>> You should use something like:
>>>>>>>
>>>>>>> header('Location: thankyou.php');
>>>>>>> die();
>>>>>> Besides the missing scheme and hostname - this was what the OP was
>>>>>> trying, but there was some output _before_ the header() call.
>>>>> And according to PHP specification, "Location" header must contain fully
>>>>> qualified address, including protocol identificator and host name.
>>>>>
>>>>> BTW, nothing wrong in sending some output before header() call... if You
>>>>> REALLY know what You doing. That all depends on Your host configuration.
>>>>>
>>>>>
>>>> Wrong. From the PHP manual under the header function:
>>>> "Remember that header() must be called before any actual output is sent,
>>>> either by normal HTML tags, blank lines in a file, or from PHP."
>>>> You CANNOT send output before a header() call. And don't try to claim
>>>> you can use ob_start(), etc. That just masks the problem, not solves it.
>>> die(0);
>>>
>>>
>
>> Which doesn't allow the header() call to be sent, among other things.
>
>> And even then, it doesn't guarantee the headers have NOT been sent already.
>
>
> That was order for Your death. You're just a disturbance and thinking that
> only Your point of view is right. So, please die without raising any
> errorlevels.
>
> I cannot send any output to the user when I have output buffering enabled
> (unless I use explicit ob_flush() call). What I mean "If You know what You
> doing". And I'm surely know what I doing by zipping output to help ppl get my
> pages quickly and successfully.
>
> I was not very precise in my words using "sending" instead of "printing", and
> I apologise for that to the rest of newsgroup.
>
> End of statement.
>
>

Good programmers fix errors. Sloppy programmers hide them with thinks
like ob_start().

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Re: using meta http-equiv in php

AnrDaemon wrote:
> Greetings, Jerry Stuckle.
> In reply to Your message dated Thursday, April 3, 2008, 02:32:32,
>
>>>>>>>>> You should use something like:
>>>>>>>>>
>>>>>>>>> header('Location: thankyou.php');
>>>>>>>>> die();
>>>>>>>> Besides the missing scheme and hostname - this was what the OP was
>>>>>>>> trying, but there was some output _before_ the header() call.
>>>>>>> And according to PHP specification, "Location" header must contain fully
>>>>>>> qualified address, including protocol identificator and host name.
>>>>>>>
>>>>>>> BTW, nothing wrong in sending some output before header() call... if You
>>>>>>> REALLY know what You doing. That all depends on Your host configuration.
>>>>>>>
>>>>>>>
>>>>>> Wrong. From the PHP manual under the header function:
>>>>>> "Remember that header() must be called before any actual output is sent,
>>>>>> either by normal HTML tags, blank lines in a file, or from PHP."
>>>>>> You CANNOT send output before a header() call. And don't try to claim
>>>>>> you can use ob_start(), etc. That just masks the problem, not solves it.
>>>>> die(0);
>>>>>
>>>>>
>>>> Which doesn't allow the header() call to be sent, among other things.
>>>> And even then, it doesn't guarantee the headers have NOT been sent already.
>>>
>>> That was order for Your death. You're just a disturbance and thinking that
>>> only Your point of view is right. So, please die without raising any
>>> errorlevels.
>>>
>>> I cannot send any output to the user when I have output buffering enabled
>>> (unless I use explicit ob_flush() call). What I mean "If You know what You
>>> doing". And I'm surely know what I doing by zipping output to help ppl get my
>>> pages quickly and successfully.
>>>
>>> I was not very precise in my words using "sending" instead of "printing", and
>>> I apologise for that to the rest of newsgroup.
>>>
>>> End of statement.
>
>> Good programmers fix errors. Sloppy programmers hide them with thinks
>> like ob_start().
>
> It is not hiding and it is not an error. It is usage of proper tools the right
> way to achieve given goals.
> I do not want to break program logic in the favor of Your "good programming".
> Call it bad logic, but it is more clear, than Your goodness. So far.
>
>

It is an error, but you're too stoopid to understand that. But that
also matches the rest of your posts here.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================