Get rid of the trailing newline after your last ?> in slib.php

Warning:  You may have configured Emacs to "add" that newline in for you
automatically.  Turn that off, if so.

Never have understood why:

<?php ... ?>
<?php ... ?>

Doesn't generate HTML output, except when ?> is the end of the file...

--
WARNING [EMAIL PROTECTED] address is an endangered species -- Use
[EMAIL PROTECTED]
Wanna help me out?  Like Music?  Buy a CD: http://l-i-e.com/artists.htm
Volunteer a little time: http://chatmusic.com/volunteer.htm
----- Original Message -----
From: Casteele/Shadowlord <[EMAIL PROTECTED]>
Newsgroups: php.general
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 22, 2001 10:52 AM
Subject: HTTP headers and include()


> I've written a separate function library for a cluster of web pages, and I
> then include("slib.php") in each of the web pages, instead of copying 12k
> of code to each page individually.  Some of the pages require (simple)
> authentication or redirection headers, which some of the code in the
> library is supposed to handle.
>
> Problem is, when I include the library, even though there's no other
output
> to be processed, it still generates the linefeed that triggers sending all
> the current headers, so if(!headers_sent) {...} fails.
>
> Is it possible to include php code without sending headers?  I've tried
> exit() within the library, but that fails to work.  Instead, exit causes
> generation of HTML code (a content type metatag) that is neither in the
> main page nor the library.  I've also tried a simple return() (per the
> documentation), but that generates a parse error.
>
> I'm using Apache 1.3.12, PHP 4.0.2 and Slackware Linux (Not sure which
> kernel version).
>
> Thanks
> Cas
>
> PS: Please CC replies to [EMAIL PROTECTED], since I'm not officially
> subscribed to this list.  Thanks.
>


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to