output-buffering

when trying to log-in at this site (user:polopolo,pass:samara) the result is a blank page. I know that the problem is with the sending of headers and the ouput_buffering in the php.ini file. I had the same problem on another host but the problem was fixed when I changed output_buffering= On . It doesn't work on the current host and I wonder why? Any suggestions? -the phpinfo of the current site. Edit: Problem solved. I reverse-engineered the code and found some additional spaces after the php closing tag, before the sending of the headers. The code wasn't written by me and I instinctively

This question already has answers here : Closed 7 years ago . Possible Duplicate: PHP - How Detect if Output Buffering is Turned On How can I check in PHP if output_buffering is set to On? I have to troubleshoot a site and I have no access to the hosting panel. Something like: if(output_buffering == 'On') { echo 'It is On'; } else { echo 'It is NOT On'; } Thank you! You should be able to do this with ini_get() . I didn't test it, but I am pretty sure it will suit your needs since ini_get() is used for that purpose: checking php.ini options. if(ob_get_level() > 0){ //there are some buffers

When I run the first code and press ctrl-c immediately there will be no 45 written out to the file. But when I run the second code, I do get 45 . I couldn't come to the reason why this behavior happens in the below code? If stdout is line buffered shouldn't output come after I enter a character? What am I missing? First code: #include<stdio.h> #include<stdlib.h> int main() { FILE *fp=stdout; fp=fopen("myfile","w"); fprintf(fp,"%d",45); getchar(); // return 0; } Second code: #include<stdio.h> #include<stdlib.h> int main() { FILE *fp=stdout; fprintf(fp,"%d",45); getchar(); // return 0; } PS: I'm

From outside SerialPort object, it seems to make no difference what the size of the write buffer is, and whether or not it is full. Using synchronous writing, the write method blocks until all the data has been sent and the buffer is empty. Using async writing, the data is queued and the program continues on going. The callback method is not called until the write operation is completed and the data is out of the buffer. The behavior of the serialport object seems to be the same regardless of how much data is in the buffer and whether or not the buffer is full. No errors seem to happen when

Suppose I am echoing random data from PHP to browser. Total amount of random data is about XGb and echo is done in YKb chunks. ob_start() is not used. Will echo calls block after PHP and Apache buffers are full (client is not capable of consuming data with the same speed it is generated)? If so, how much in size PHP and Apache buffers? Do I understand correctly, the process: PHP echo is sending bytes to php output buffer until it is full. After that echo starts to block until some buffer is sent to Apache and thus cleared PHP is sending data from it's output buffer until Apache buffer is full.

My site's admin section has a bunch of very slow report-generating scripts that echo output line by line as it is generated. To have this output flushed immediately to the browser, instead of the user having to wait for minutes before they see any response, we have output_buffering disabled and we call ob_implicit_flush at the beginning of such scripts. For convenience, I was considering just turning on the implicit_flush setting in php.ini instead of adding ob_implicit_flush() calls to every script that would benefit from it. However, the documentation contains the following scary but

What are the methods to turn on output buffering either within a PHP script or using and htaccess file? I use the following method in an htaccess file in the root of my application: php_value output_buffering On php_value output_handler mb_output_handler On one of my shared hosting accounts (linux hosting with PHP 5.2.x), the above yields a blank page. Tech support says they can't turn it on in the php.ini file but I can turn it on in my script... ob_start() and ob_end_flush() also yields the same result. What can I do? Diablo Use ob_start() and ob_end_flush() . ob_start() at the start of the