file upload size problem
vamsy krishna
I'm doing a file upload from one of my forms and writing the content
to a temp file on the server. The problem is any file of size more
than 250 KB is throwing the below error:
Request Entity Too Large
The requested resource
/tera/tera_upload/
does not allow request data with POST requests, or the amount of data
provided in the request exceeds the capacity limit.
I read through the django file uploads documentation and it says the
default file upload size in memory is about 2.5 MB. Can anyone tell me
what I'm overlooking? Also how do I set a maximum file size limit and
handle it?
Thanks,
Vamsy
Karen Tracey
Karen
--
http://tracey.org/kmt/
vamsy krishna
vamsy krishna
using the handler413 in my urls file to load this template. However
this is not getting picked up. I would like to handle this at django
level instead of apache. The ErrorDocument definition in apache works
fine.
Also the handler404 and handler500 are working without any issue. Can
someone point me in the right direction?
Thanks,
Vamsy
Tom Evans
> I'm facing a new problem now. I have a defined a custom error page and
> using the handler413 in my urls file to load this template. However
> this is not getting picked up. I would like to handle this at django
> level instead of apache. The ErrorDocument definition in apache works
> fine.
>
> Also the handler404 and handler500 are working without any issue. Can
> someone point me in the right direction?
>
> Thanks,
> Vamsy
>
handler404 and handler500 get called if django tries to serve a page
that doesn't exist or a page that errors. Your 413 is generated from
apache, and so does not ever call django, therefore django cannot
handle this error.
To get around this, set
ErrorHandler 413 /some/django/url
Apache will use an internal redirect to fetch this URL, so it should
be transparent to your users.
Cheers
Tom
vamsy krishna
handler413 defined. I'm now doing it in apache the way you mentioned.
On Mar 14, 4:38 pm, Tom Evans <tevans...@googlemail.com> wrote:
vamsy krishna
I've set a custom error page for the 413 error when the upload file
size exceeds the maximum set in apache LimitRequestBody directive (500
KB).
This is working fine for all files upto 3 MB. However when the size
exceeds this limit, the browser is showing the below message instead
of my custom error page. Can someone point me in the right direction?
Connection Interrupted
The connection to the server was reset while the page was
loading.
The network link was interrupted while negotiating a connection.
Please try again.
Thanks,
Vamsy
Michal Petrucha
> > size exceeds the maximum set in apache LimitRequestBody directive (500
> > KB).
> > This is working fine for all files upto 3 MB. However when the size
> > exceeds this limit, the browser is showing the below message instead
> > of my custom error page. Can someone point me in the right direction?
> >
> > Connection Interrupted
> >
> > The connection to the server was reset while the page was
> > loading.
> >
> > The network link was interrupted while negotiating a connection.
> > Please try again.
request size exceeds some multiple of the limit.
I think this is reasonable, just imagine that somebody would try to
upload for example /dev/urandom or /dev/zero (i. e. an infinite amount
of data). Would you want the server to suck it all in and then give an
error message saying that the limit has been exceeded?
Michal Petrucha
vamsy krishna
vamsy krishna
back a 413 response as soon as it finds the huge mismatch in the
upload limit and the actual upload size. Also I think the server
immediately terminates the connection for the request. The problem
however is that the browser instead of reading the response from the
server shows the connection interrupted message. Ideally I would like
to configure it in a way the 413 error page is shown instead. Or do
you think it is not feasible in such a case?
Regards,
Vamsy
> < 1KViewDownload
Tom Evans
> That is true Michal. My understanding is that the server does send
> back a 413 response as soon as it finds the huge mismatch in the
> upload limit and the actual upload size. Also I think the server
> immediately terminates the connection for the request. The problem
> however is that the browser instead of reading the response from the
> server shows the connection interrupted message. Ideally I would like
> to configure it in a way the 413 error page is shown instead. Or do
> you think it is not feasible in such a case?
>
> Regards,
> Vamsy
>
Think for a moment about how this works. You've set the upload limit
to 500k. If you start uploading more than this, then the web server
can really only do one thing, it can send you a 413 response and close
the connection.
If your browser then tries to continue to upload the file, it will try
to write data to a closed socket connection, and fail. If it's smart,
it will then see if there is a response to read from the socket,
otherwise it will display a cryptic 'connection interrupted' message.
Try the same test in a bunch of browsers; I bet Opera will handle it
correctly.
You've asked for the connection to be interrupted, by setting
LimitRequestBody. It can't both limit the request body size, and wait
for a client to be ready to read the error response.
Cheers
Tom
vamsy krishna
Opera.
On Mar 17, 2:47 pm, Tom Evans <tevans...@googlemail.com> wrote: