[Tickets #7851] Re: "Headers already sent" caused by usage of flush()

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7851
------------------------------------------------------------------------------
  Ticket             | 7851
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | "Headers already sent" caused by usage of flush()
  Queue              | DIMP
  Version            | 1.1.1
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2009-01-15 14:03) wrote:

> There has been added a flush() call in DIMP.php between revision 1.131
> and 1.132 - causing thousands of warning lines a day in my syslog:
>
>> Cannot modify header information - headers already sent in Unknown on line 0

This will happen if you have extra space at the top of one of your  
config files.

> I'm running latest Debian Lenny, PHP 5.2.6 (untouched, from Lenny) as an
> Apache Module, APC Cache enabled.
>
> See http://cvs.horde.org/diff.php/dimp/lib/DIMP.php?r1=1.131&r2=1.132
> for the exact change (not documented in CVS log).
>
> Removing the flush()-call solves this issue, no more warnings since then.

That is correct - DIMP will catch any unexpected input at the very end  
of processing and toss it - but will also this unexpected output at a  
DEBUG level to the Horde log.  So this has probably been an issue  
forever - you simply haven't seen it because you are not logging at a  
DEBUG level.