Re: Re: PHP cuts download process prematurely
| From: | Manuel Barros Reyes | Date: | Tue, 26 Feb 2008 14:31:58 +0000 |
| Subject: | Re: Re: PHP cuts download process prematurely | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-270147@lists.php.net to get a copy of this message | ||
On Tue, Feb 26, 2008 at 3:07 AM, Andrés Robinet <agrobinet@bestplace.biz> wrote:
>
> Though this is not likely to solve the problem, try adding the following two
> lines at the beginning of the script (even before you query the database and do
> all your logic)
>
> ignore_user_abort(true);
> set_time_limit(0);
>
> You need the log files to know exactly what the problem is. And, even if you are
> not solving this issue using compression as a workaround, you may also want to
> add at the beginning of the script:
>
> ob_start("ob_gzhandler")
From what I read I think ob_start("ob_gzhandler") would be needed if I
would like to compress output transparently and let the clients
browser do the reverse job in the same maner, but in this case I am
uploading the files as .gz and the person who downloads it takes care
of decompressing it by hand.
Maybe I should use a simple ob_start() in this case. I understand
ob_start()-ob_end_flush() collects data in a server buffer and outputs
it all together but in the case of my script the only output is the
file I am uploading and the output is only in th echo $contents.
Unless I am missing details of ob_start() wouldn't this be equivalent
in this case?
Thanks