Re: File Upload - post_max_size and upload_max_filesize in GBs
| From: | Abdullah Ramazanoglu | Date: | Thu, 07 Jun 2007 22:37:20 +0000 |
| Subject: | Re: File Upload - post_max_size and upload_max_filesize in GBs | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-256332@lists.php.net to get a copy of this message | ||
Sukhwinder Singh dedi ki:
--8<--
> I have read. I have been trying to find out way for last two days.
> I can say about jupload and how it seems to work.
> It uploads file to server in a temporary directory.
> It has postURL parameter. Then it POSTS the data to php file.
> Because it POSTS, the php configuration values comes into question.
>
> Here is an example:
>
> Settings in php.ini are 50M for upload_max_fisesize and 50M for
> post_max_size.
> I used japplet and uploaded a 51.89 MB file.
>
> This is what is in error log.
>
> [08-Jun-2007 03:06:29] PHP Warning: POST Content-Length of 54414946
> [bytes
> exceeds the limit of 52428800 bytes in Unknown on line 0
Sorry but I couldn't follow. If I understood correctly, there's 50M (or 4G,
for that matter) data, and there's say 5K metadata. First, java applet
uploads the bulk data over ftp to a temp directory on the server
(employing the ftp service running on the server - not apache/php).
If/when the bulk data transfer completes successfully, then the java
applet needs to POST the 5K metadata over http to php. Up to this point I
can follow. But in your example, the java applet transfers the bulk data
itself -not metadata- a second time, POSTing it to php?
If so, then the applet you use (or the parameters it's been passed) should
be broken, I guess.
Kind regards,
--
Abdullah Ramazanoglu
aramazan ÄT myrealbox D0T cöm