Yes Tom, thanks. That makes sense. And yes it works like a charm on Opera. On Mar 17, 2:47 pm, Tom Evans <tevans...@googlemail.com> wrote: > On Thu, Mar 17, 2011 at 6:51 AM, vamsy krishna <badguitar...@gmail.com> wrote: > > 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
-- 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.
