Re: able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- From: The Natural Philosopher <a@xxx>
- Date: Sat, 31 May 2008 18:12:24 +0100
MikeB wrote:
On May 31, 6:38 am, "C. (http://symcbean.blogspot.com/)"
<colin.mckin...@xxxxxxxxx> wrote:
If you set the limit in the webserver config then it will terminate
the conenction.
I probably should not get involved in a discussion like this, but I
can't help it. If the purpose is to save bandwidth, does the webserver
terminate the connection *after* if has uploaded to the specified
limit?
The webserver doesn't KNOW what php's bandwidth limit is. It takes ALL the POST data of which the uploaded file is part, and gives it to PHP.
If tat is the case, that would be wasteful for an upload. Is there not.
a facility that one could write just before the upload function is
involved to check the size of the file on the client and not start the
upload at that point? That would seem to be more bandwidth-sensible?
- Follow-Ups:
- References:
- able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- From: Lawrence Krubner
- Re: able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- From: C. (http://symcbean.blogspot.com/)
- Re: able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- From: MikeB
- able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- Prev by Date: Re: Feedback wanted: new PHP template engine
- Next by Date: Re: Interactive mode not very useful
- Previous by thread: Re: able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- Next by thread: Re: able to upload 28 meg file, yet php.ini limits posts to 10 megs. What is up with that?
- Index(es):
Relevant Pages
|
