[imp] Error handling for files that are too big for the web server

Claude Tompers claude.tompers at restena.lu
Fri Jan 31 12:23:25 UTC 2014


On Fri, 31 Jan 2014 11:51:30 +0100
Jan Schneider <jan at horde.org> wrote:

> 
> Zitat von Claude Tompers <claude.tompers at restena.lu>:
> 
> > On Fri, 31 Jan 2014 10:43:59 +0100
> > Jan Schneider <jan at horde.org> wrote:
> >
> >>
> >> Zitat von Claude Tompers <claude.tompers at restena.lu>:
> >>
> >> > On Tue, 28 Jan 2014 16:13:52 +0100
> >> > Jan Schneider <jan at horde.org> wrote:
> >> >
> >> >>
> >> >> Zitat von Claude Tompers <claude.tompers at restena.lu>:
> >> >>
> >> >> > Hello,
> >> >> >
> >> >> > Using the latest version of IMP, if I try to upload a file
> >> >> > that is too big for the web server itself to accept (sending
> >> >> > back a 413 error page), Horde is unable to handle the
> >> >> > response and stays in an "pending" state. If PHP has to
> >> >> > handle the problem, everything works fine.
> >> >> >
> >> >> > kind regards,
> >> >> > Claude Tompers
> >> >>
> >> >> Yes.
> >> >
> >> > Is there a way to fix this problem so that Horde does not "fail"
> >> > silently ?
> >>
> >> No, because it isn't Horde that fails.
> >
> > Well failing is the wrong term, the JavaScript function handling the
> > XHR request ignores the fact that it gets a 413 status back instead
> > of a 200 status. Shouldn't Horde tell the user about that ?
> 
> If the javascript library (prototype) is providing this information,
> yes.

Is prototype.js providing this information and are you going to fix
this issue at some point ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.horde.org/archives/imp/attachments/20140131/0b0564d4/attachment.bin>


More information about the imp mailing list