Yes Tom, thanks. That makes sense. And yes it works like a charm on
Opera.
On Mar 17, 2:47 pm, Tom Evans wrote:
> On Thu, Mar 17, 2011 at 6:51 AM, vamsy krishna wrote:
> > That is true Michal. My understanding is that the server does send
> > back a 413 response as soon as it finds the huge mism
On Thu, Mar 17, 2011 at 6:51 AM, vamsy krishna 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 f
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
> > 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 instea
Any suggestions please?
On Mar 15, 12:18 pm, vamsy krishna wrote:
> Hi All,
>
> 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
Hi All,
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 cus
Thanks Tom. I also looked up the Django code and realised there is no
handler413 defined. I'm now doing it in apache the way you mentioned.
On Mar 14, 4:38 pm, Tom Evans wrote:
> On Mon, Mar 14, 2011 at 9:02 AM, vamsy krishna wrote:
> > I'm facing a new problem now. I have a defined a custom err
On Mon, Mar 14, 2011 at 9:02 AM, vamsy krishna wrote:
> 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
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 handl
Oh yes. Thanks Karen.
On Mar 12, 7:06 pm, Karen Tracey wrote:
> On Sat, Mar 12, 2011 at 12:06 AM, vamsy krishna wrote:
>
> > 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
On Sat, Mar 12, 2011 at 12:06 AM, vamsy krishna wrote:
> 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
> /ter
11 matches
Mail list logo