Use case for output buffering as the correct solution to "headers already sent"
Posted
by kemp
on Stack Overflow
See other posts from Stack Overflow
or by kemp
Published on 2010-05-27T08:34:02Z
Indexed on
2010/05/27
9:01 UTC
Read the original article
Hit count: 256
php
|output-buffering
I see (not just on this site) a lot of question from inexperienced PHP programmers about the infamous "headers already sent... output started at" error, and many people suggest using ouput buffering as a solution.
In my experience I have never found a situation where that error wasn't caused by a flow in the program's logic. Are there cases where output buffering is actually the correct solution?
© Stack Overflow or respective owner