Alexander Ross wrote:
>ok ... but the line of code that was the culprit was simply:
>
>print "var id = ".$id.""; //for debugging
>
>how does that line constitute sending more header info?
>
It does not constitute sending more headers, but it does say that no
more may be sent (as you have already
When you request a page, for instance, php.net, your web browser sends HTTP headers to
the server that holds php.net on it. When the server receives these HTTP headers, it
knows which page is needed, and sets up it's own headers to send back to the browser,
such as location, file types, etc.
ok ... but the line of code that was the culprit was simply:
print "var id = ".$id.""; //for debugging
how does that line constitute sending more header info?
Alex
"Chris Hewitt" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Alexander Ross wrote:
>
> >I'm
Alexander Ross wrote:
>I'm slowly beginning to undrestand this, but please bear with a php novice.
>When/how were the headers sent? In other words, how do I know that they
>have already been sent?
>
Because something other than a header has gone out. As something other
has gone out, it is not p
4 matches
Mail list logo
