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 On Mar 16, 9:36 pm, Michal Petrucha <johnn...@ksp.sk> wrote: > > > 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. > > My guess is that the webserver hangs up as soon as it sees the > 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 > > signature.asc > < 1KViewDownload -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
