# main/output.c problem

- Thread: https://externals.io/message/57816
- Original archive: https://news-web.php.net/php.internals/57816
- Started by James Edmunds on 2012-02-13T08:54:38+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #57816 — James Edmunds — 2012-02-13T08:54:38+00:00

URL: https://externals.io/message/57816#57816

The new output buffering mechanism has a compatibility function for people 
/ extensions that use the "old way". There is a compatibility function 
php_output_handler_compat_func(). It is not quite as compatible as it 
should be, and any code that depends on it will break. Using the "old way" 
if the output handler function set the return buffer pointer to NULL, it 
was a signal to the output code to pass through the buffer contents 
unmodified. The compatibility function wasn't doing that. The patch below 
fixes that. Sorry if this message doesn't follow normal procedures, I have 
very limited time and wanted to make sure I reported this before 5.4 ships. 
Hopefully the powers that be will considering including it.

Thanks in advance.

---

## #57880 — Michael Wallner — 2012-02-14T19:34:24+00:00

URL: https://externals.io/message/57816#57880 · In reply to: #57816

...
> if the output handler function set the return buffer pointer to NULL, it
> was a signal to the output code to pass through the buffer contents
> unmodified. The compatibility function wasn't doing that. 

A fix has been committed.  Thank you for the report!

Regards,
Mike